Re: addIndexesNoOptimize question

2008-12-19 Thread Antony Bowesman
Thanks Mike, I'm still on 2.3.1, so will upgrade soon. Antony Michael McCandless wrote: This was an attempt on addIndexesNoOptimize's part to "respect" the maxMergeDocs (which prevents large segments from being merged) you had set on IndexWriter. However, the check was too pedantic, and was

Re: addIndexesNoOptimize question

2008-12-18 Thread Michael McCandless
This was an attempt on addIndexesNoOptimize's part to "respect" the maxMergeDocs (which prevents large segments from being merged) you had set on IndexWriter. However, the check was too pedantic, and was removed as of 2.4, under this issue: https://issues.apache.org/jira/browse/LUCENE

addIndexesNoOptimize question

2008-12-17 Thread Antony Bowesman
The javadocs state "This requires ... and the upper bound* of those segment doc counts not exceed maxMergeDocs." Can one of the gurus please explain what that means and what needs to be done to find out whether an index being merged fits that criteria. Thanks Antony