[
https://issues.apache.org/jira/browse/LUCENE-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493441
]
Mark Miller commented on LUCENE-874:
------------------------------------
I agree that there should be a Sandbox endorsed solution to the very common
need of a live, interactive index. Solr is great if you want to move beyond
Lucene, but not everyone wants to use Solr. There are probably a lot of custom
management systems out there to handle index access for a live system and I
think there would be a lot of benefit to new users to standardize some of that,
especially considering how often people seem to get it wrong when trying to do
this themselves (multiple index writers and searchers, etc). IndexModifier is a
step in that direction, but a lot more could be done. A lot of pieces are
already around:
Lucene-390 : this class is great. It has a few shortcoming and could use some
improvements and extending (warming searchers), but it is a very solid base for
such things.
Lucene-112 : probably outdated, but some ideas for keeping a reader fresh.
I know there are others as well.
The new IndexWriter that can delete is a great help in this regard as well,
especially in combination with Lucene-390. Deleting used to involve releasing a
writer, getting a writing reader and then doing the delete. This made batching
extremely important...with IndexWriter now able to delete, you don't have to
rely nearly as much on batching...reindexing in an object oriented environment
can become much faster and designs can simplify.
- Mark
> Automatic reopen of IndexSearcher/IndexReader
> ---------------------------------------------
>
> Key: LUCENE-874
> URL: https://issues.apache.org/jira/browse/LUCENE-874
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Search
> Reporter: João Fonseca
> Priority: Minor
>
> To improve performance, a single instance of IndexSearcher should be used.
> However, if the index is updated, it's hard to close/reopen it, because
> multiple threads may be accessing it at the same time.
> Lucene should include an out-of-the-box solution to this problem. Either a
> new class should be implemented to manage this behaviour (singleton
> IndexSearcher, plus detection of a modified index, plus safely closing and
> reopening the IndexSearcher) or this could be behind the scenes by the
> IndexSearcher class.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
