[
https://issues.apache.org/jira/browse/LUCENE-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-1014.
----------------------------------------
Resolution: Won't Fix
I don't think we can cleanly fix this w/o breaking backwards compatibility.
If it's really important you can always create a custom MergePolicy which does
respect maxMergeDocs during optimize.
> IndexWriter.optimize() does not respect maxMergeDocs
> ----------------------------------------------------
>
> Key: LUCENE-1014
> URL: https://issues.apache.org/jira/browse/LUCENE-1014
> Project: Lucene - Java
> Issue Type: Bug
> Components: Index
> Affects Versions: 1.9, 2.0.0, 2.0.1, 2.1, 2.2, 2.3
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Priority: Minor
>
> Similar to LUCENE-1012, IndexWriter.optimize() does not respect
> maxMergeDocs: it always merges the index down to one segment.
> I don't think we should change this for the existing optimize() since
> this would be a change in behavior. I think instead in doing
> LUCENE-982 (adding IndexWriter.optimize(int maxNumSegments) method) we
> can have it respect maxMergeDocs.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
