[
https://issues.apache.org/jira/browse/LUCENE-3454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114568#comment-13114568
]
Jan Høydahl commented on LUCENE-3454:
-------------------------------------
I've seen people optimize after every single add(). Even the Django search
framework Solango did this terrible mistake.
So I think renaming is welcome, and now that Lucene does such a good merging
job for you most people won't need optimize. How about:
reduceSegments(int numSegments)
Does it convey the "maybeness" well enough? If I use it I need to know what a
segment is and have some feeling for how many segments there are and how many I
want, so its usage will imply some knowledge. But maybeMerge() works as well.
> 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
