[
https://issues.apache.org/jira/browse/LUCENE-3454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114283#comment-13114283
]
Shai Erera commented on LUCENE-3454:
------------------------------------
It's just that maybeMerge feels like asking a question, to which you expect an
answer. Why is it so important to have this 'maybe' or 'ifNeeded' in the API?
just like optimize(), MP decides what to merge, and optimize() can end up doing
nothing as well ...
Why do we have IR.reopen and not maybeReopen? That that it returns something is
not much different than IW.merge(), IMO.
> 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
