Re: Lucene.Net 2.1 status

[Simone Busoli]

Hi George, thanks for the update. I wanted to ask you something about 2.1. In Java Lucene FAQ one of the entries says: Why do I have a deletable file (and old segment files remain) after running optimize? This is normal behavior on Windows whenever you also have readers (IndexReaders or IndexSearchers) open against the index you are optimizing. Lucene tries to remove old segments files once they have been merged (optimized). However, because Windows does not allow removing files that are open for reading, Lucene catches an IOException deleting these files and and then records these pending deletable files into the "deletable" file. On the next segments merge, which happens with explicit optimize() or close() calls and also whenever the IndexWriter flushes its internal RAMDirectory to disk (every IndexWriter.DEFAULT_MAX_BUFFERED_DOCS (default 10) addDocuments), Lucene will try again to delete these files (and additional ones) and any that still fail will be rewritten to the deletable file. Note that as of 2.1 the deletable file is no longer used. Instead, Lucene computes which files are no longer referenced by the index and removes them whenever a writer is created. I'm working on Lucene.Net trunk but I still get the deletable-files-not-deleted behavior under Windows. Is this supposed to be working instead? Simone George Aroush wrote: Hi folks, Lucene.Net 2.1 is stabilizing very well. Thanks to DIGY who flushed out the last remaining NUnit failed tests, we are now down to only one test that is failing: Lucene.Net.Index.TestNorms._TestNorms(). Since Monday, I have been using this version in production with success. I like to get feedback from others if you are using it and how it's working for you. If results are good, and pending the elimination of Lucene.Net.Index.TestNorms._TestNorms() I think we are ready to vote on this release and close it. As for the next step, I'm going to take a look at Lucene Java 2.2 and see how big of a job to port it will be. I will post on it in few days. Regards, -- George