lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] Updated: (LUCENE-1013) IndexWriter.setMaxMergeDocs gives non-backwards-compatible exception "out of the box"
Date Wed, 03 Oct 2007 16:42:50 GMT


Michael McCandless updated LUCENE-1013:

    Attachment: LUCENE-1013.patch

Attached patch to move setMaxMergeDocs up into LogMergePolicy so that IndexWriter.setMaxMergeDocs(...)
works out-of-the-box again.  I plan to commit in a few days.

> IndexWriter.setMaxMergeDocs gives non-backwards-compatible exception "out of the box"
> -------------------------------------------------------------------------------------
>                 Key: LUCENE-1013
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Index
>    Affects Versions: 2.3
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: 2.3
>         Attachments: LUCENE-1013.patch
> Yonik hit this (see details in LUCENE-994): because we have switched
> to LogByteSizeMergePolicy by default in IndexWriter, which uses MB to
> limit max size of merges (setMaxMergeMB), when an existing app calls
> setMaxMergeDocs (or getMaxMergeDocs) it will hit an
> IllegalArgumentException on dropping in the new JAR.
> I think the simplest solution is to fix LogByteSizeMergePolicy to
> allow setting of the max by either MB or by doc count, just like how
> in LUCENE-1007 allows flushing by either MB or docCount or both.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message