[ https://issues.apache.org/jira/browse/LUCENE-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494026 ]
João Fonseca commented on LUCENE-874: ------------------------------------- > I would consider a JMS solution on top of NotifiableIndex (or your own > factory). JMS seems to be a complicated and heavy solution to a simple and recurring problem for those using Lucene: you want to use a singleton IndexSearcher to improve performance, but when the index changes, you want the IndexSearch to show the updated information. > 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]