[jira] Resolved: (LUCENE-1254) addIndexesNoOptimize should not enforce maxMergeDocs/maxMergeSize limit

["Michael McCandless (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LUCENE-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael McCandless resolved LUCENE-1254.
----------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.3.2

> addIndexesNoOptimize should not enforce maxMergeDocs/maxMergeSize limit
> -----------------------------------------------------------------------
>
>                 Key: LUCENE-1254
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1254
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Index
>    Affects Versions: 2.1, 2.2, 2.3
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>            Priority: Trivial
>             Fix For: 2.3.2, 2.4
>
>         Attachments: LUCENE-1254.patch
>
>
> If you pass an index that has a segment > maxMergeDocs or maxMergeSize
> to addIndexesNoOptimize, it throws an IllegalArgumentException.
> But this check isn't reasonable because segment merging can easily
> produce segments over these sizes since those limits apply to each
> segment being merged, not to the final size of the segment produced.
> So if you set maxMergeDocs to X, build up and index, then try to add
> that index to another index that also has maxMergeDocs X, you can
> easily hit the exception.
> I think it's being too pedantic; I plan to just remove the checks for
> sizes.

-- 
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: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org