[
https://issues.apache.org/jira/browse/ISIS-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662908#comment-13662908
]
Martin Grigorov commented on ISIS-383:
--------------------------------------
I'd suggest to use ElasticSearch or Solr instead of plain Lucene.
The main problem with Lucene is its clustering. For example if you use Isis in
a clustered environment (web server with several nodes) then a Lucene
writer/reader pair will run on every node. Since Lucene doesn't support by
itself clustered indexes and two IndexWriters cannot write to the same
FSDirectory any entity stored at node1 will be written in the DB and the
indexes for Lucene1. Later any searches on all nodes but node1 won't have the
new data (until they recreate their indexes from the DB).
I'd recommend to use ElasticSearch instead. It supports this use case for free.
> [GSOC2013] integrate Apache Lucene with Apache Isis as a generic text search
> engine
> -----------------------------------------------------------------------------------
>
> Key: ISIS-383
> URL: https://issues.apache.org/jira/browse/ISIS-383
> Project: Isis
> Issue Type: New Feature
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Labels: gsoc, gsoc2013
> Attachments: isis-lucene.zip
>
>
> Isis is most often used with its JDO integration, a fairly conventional ORM.
> Searching for existing domain objects therefore requires a query to be
> defined.
> But sometimes users want to just search for any object (like searching the
> web). This ticket is to integrate Isis so that its domain objects can be
> indexed by Lucene and thus provide a generic search capability.
> One way to get hold of the text (to be indexed) might be to use the existing
> capability to convert all objects into JSON (by the
> isis-restfulobjects-rendering module).
> It is also pretty easy to hook into Isis' objectstore to know when an object
> is being updated (to sync with Lucene's indexes).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
