Re: IndexReader.isCurrent for cached indexes

2009-09-10 Thread Nick Bailey
n. On Wed, Sep 9, 2009 at 10:33 PM, Nick Bailey wrote: > Looking for some help figuring out a problem with the IndexReader.isCurrent() > method and cached indexes. > > We have a number of lucene indexes that we attempt to keep in memory after an > initial query is performed.  

IndexReader.isCurrent for cached indexes

2009-09-09 Thread Nick Bailey
dex should have been reopened after the second delete. I have checked, and the code to refresh the indexes is definitely being run every 60 seconds.  All I can see is that the problem might be with the isCurrent() method.   Could it be due to holding the reader open for so long? Any other ideas?