Re: IndexReader.isCurrent for cached indexes

2009-09-10 Thread Nick Bailey
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: [email protected] Subject: Re: IndexReader.isCurrent for cached indexes isCurrent() will only return true if there have been comm

Re: IndexReader.isCurrent for cached indexes

2009-09-10 Thread Ian Lea
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.