OK, I opened LUCENE-1254 and committed the fix to trunk & (upcoming)
2.3.2.
Mike
Yonik Seeley wrote:
On Mon, Mar 31, 2008 at 5:19 AM, Michael McCandless
<[EMAIL PROTECTED]> wrote:
I think we should remove those checks and allow addIndexesNoOptimize
to import and index even if it has segm
On Mon, Mar 31, 2008 at 5:19 AM, Michael McCandless
<[EMAIL PROTECTED]> wrote:
> I think we should remove those checks and allow addIndexesNoOptimize
> to import and index even if it has segments over this limit. I'll
> open an issue.
+1
-Yonik
---
This happens when addIndexesNoOptimize finds a segment that's larger
than maxMergeDocs in the index(es) it's given.
If you leave maxMergeDocs at Integer.MAX_VALUE it will fix that.
Though really it's being a little too pedantic because that setting
(maxMergeDocs) sets the maximum size of a
