lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wettin (JIRA)" <>
Subject [jira] Commented: (LUCENE-874) Automatic reopen of IndexSearcher/IndexReader
Date Sat, 05 May 2007 16:42:15 GMT


Karl Wettin commented on LUCENE-874:

João Fonseca [04/May/07 04:49 AM]
> AutofreshedSearcher seems to be something like what I was proposing, but it 
> seems to rely on the NotifiableIndex mechanism. Will this work if the task that 
> updates the index is on another process/JVM?

No, it is a single JVM solution.

> The problem is when the index is modified (which, in my case, is done by an
> external process, from time to time). The IndexSearcher must be reopened. There
> are several issues to solve: 

I would consider a JMS solution on top of NotifiableIndex (or your own factory).

> Automatic reopen of IndexSearcher/IndexReader
> ---------------------------------------------
>                 Key: LUCENE-874
>                 URL:
>             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:
For additional commands, e-mail:

View raw message