according to what I say is the expected behavior. Until you open another reader lucene won't delete the old index files left behind. if you open the index with luke you are using a reader and cleaning the old files.
to ensure I'm correct you can open a reader with lucene.net after the step 5 to test if it deletes the remaining files. jokin On 7/18/07, Simone Busoli <[EMAIL PROTECTED]> wrote:
I'm using the latest release of Lucene.Net. Here's the steps of the application: 1. create index 2. open index reader to remove stuff 3. close index reader 4. open index writer to add stuff 5. optimize and close index writer 2-5 are repeated at intervals. So there's always at most one object writing to the index at one point in time. Not a big issue after all, but thanks for your help. Simone
