[
https://issues.apache.org/jira/browse/LUCENE-3454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114154#comment-13114154
]
Robert Muir commented on LUCENE-3454:
-------------------------------------
Otis: thats a good point, currently optimize is just a "request", we should
probably figure out what it "should be".
Should it be collapseSegments, which is a well-defined request without a cool
sounding name?
Or, should it be <something else>, which gives you a more optimal configuration
for search performance... (i still think optimize is a bad name even for this)?
Personally i suspect its going to be hard to support this case, e.g. you would
really need to know things like, if the user has executionService set on the
IndexSearcher and how big the threadpool is and things like that to make an
'optimal' configuration... and we don't have a nice way of knowing that
information today.
> 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: [email protected]
For additional commands, e-mail: [email protected]
