Re: Doubt on IndexWriter.close()

Hi Mike. Our project currently uses 2.0.0. So I suppose the later versions might not be allowing this, right? Ajay Garg Michael McCandless-2 wrote: > > Which version of Lucene are you using? Recent versions do not allow > addDocument to be called after close. > > Mike > > java_is_everythi

Pooling indexReader

Hi: I had some code to do indexReader pooling to avoid open and close on a large index when doing lotsa searches. So I had a FilteredIndexReader proxy that overrides the doClose method to do nothing, and when I really want to close it, I call super.doClose(). This patter worked well for me prior

Re: document retrieval 100 times slower after finishing some heavy disk operation

yes, we have seen this many times. The problem is, especially on windows ,that some simple commands like copy make havoc of File System cache, as matter of fact, we are not sure it is the cache that is making problems, generally all IO operations start blocking like crazy (we have seen this effe

Re: Preventing index corruption

Thanks for the information. >From what I read in other posts it's better to prevent using RAMDirectory since the same result can be achieved by using the autoCommit=false as you suggested. I'm using 2.3.1 so I guess I'll have to wait to 2.4 or take the latest trunk in order to benefit from these