Re: IndexReader.close() behavior

2011-05-13 Thread Mindaugas Žakšauskas
Hi, In my quest to fight a similar problem, I ended up writing a wrapper finalizer (sic!) that simply closes the underlying reader/searcher. It might be against all advices (e.g. "Effective Java 2ed" Item 7) but I simply couldn't find any better solution to this problem. I wish I wouldn't need do

RE: IndexReader.close() behavior

2011-05-13 Thread Alexey Lef
that it is not easy to change something that's been working in a particular way for years. Thanks, Alexey -Original Message- From: Michael McCandless [mailto:luc...@mikemccandless.com] Sent: Tuesday, April 26, 2011 11:20 PM To: java-user@lucene.apache.org Subject: Re: IndexReader.c

Re: IndexReader.close() behavior

2011-04-26 Thread Michael McCandless
The code is tricky, but it's intentional. We always set closed to true to guard against double close, ie, it's fine to double-close an IndexReader, ie doing so will not "steal" references from other places that have incRef'd the reader. Can you pass closeSubReaders=false when you create your Mult