After reading all about the renaming of optimize() and updating my Lucene libraries to 3.4, I was surprised and confused by what I found.
I have a 1 segment index (all files are named _1*.*) that had been created with 3.0.1 code which had been optimized many times (all 3.0.1 code). The first time my code used the 3.4 libraries with version level set to 3.4 and it tried to optimize() (still using this now deprecated old call), the new code went wild! It took up more memory than the heap was limited to, so I believe it is taking up system resources. We have turned off optimize for now. What is it doing? (I believe it is using a TieredMergePolicy, see the IndexWriter constructor). Anyone have any resources to point me to on the subject so I can pick the right call to forceMerge() and a good MergePolicy before upgrading to Lucene 4.0? Any ideas? What should be a reasonable 3.4 approach? Are there issues about the the just complete IndexWriter? Ho about open readers (in the web app using the index). -Paul p.s. More details available upon request. --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
