[
https://issues.apache.org/jira/browse/LUCENE-3454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114248#comment-13114248
]
Michael McCandless commented on LUCENE-3454:
--------------------------------------------
How about maybeMerge() and maybeMerge(int maxSegCount) (since we have to absorb
optimize(int maxSegCount) too)?
This way what used to be optimize is now maybeMerge(1).
I like that this forces the user to make an explicit decision about how many
segments they require the index to merge down to, so they realize by picking 1
they are asking for tons of merging.
> rename optimize to a less cool-sounding name
> --------------------------------------------
>
> Key: LUCENE-3454
> URL: https://issues.apache.org/jira/browse/LUCENE-3454
> Project: Lucene - Java
> Issue Type: Improvement
> Affects Versions: 4.0
> Reporter: Robert Muir
>
> I think users see the name optimize and feel they must do this, because who
> wants a suboptimal system? but this probably just results in wasted time and
> resources.
> maybe rename to collapseSegments or something?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
