[
https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211439#comment-13211439
]
Yonik Seeley commented on SOLR-3141:
------------------------------------
And if we did change, naive users would be:
"oh, optimize doesn't work any more..." (looks up what it's been changed to)
"ok, changed to forceMerge."
After forceMerge is out there for a while, it would have the same problem as
optimize. Someone tries it, their queries run faster, and it gets passed along
as something to try to speed things up (and it is in the right scenario). The
correct path here is to document it correctly, and get rid of any bad examples
in our documentation.
Someone can add a big fat message at the top of CHANGES explaining the cost of
optimize and the fact that it's often less necessary than it was in the past if
they want.
> Deprecate OPTIMIZE command in Solr
> ----------------------------------
>
> Key: SOLR-3141
> URL: https://issues.apache.org/jira/browse/SOLR-3141
> Project: Solr
> Issue Type: Improvement
> Components: update
> Affects Versions: 3.5
> Reporter: Jan Høydahl
> Labels: force, optimize
> Fix For: 3.6
>
>
> Background: LUCENE-3454 renames optimize() as forceMerge(). Please read that
> issue first.
> Now that optimize() is rarely necessary anymore, and renamed in Lucene APIs,
> what should be done with Solr's ancient optimize command?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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]
