m but didn't think it was related.
We are running 2.4.1
-Original Message-
From: "Ian Lea"
Sent: Thursday, September 10, 2009 5:05am
To: java-user@lucene.apache.org
Subject: Re: IndexReader.isCurrent for cached indexes
isCurrent() will only return true if there have been comm
isCurrent() will only return true if there have been committed changes
to the index. Maybe for some reason your index update job hasn't
committed or closed the index.
Probably not relevant to this problem, but your reopen code snippet
doesn't close the old reader. It should. See the javadocs.
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. In order to prevent the indexes from becoming
stale, we check for changes about e
