[
https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211575#comment-13211575
]
Uwe Schindler edited comment on SOLR-3141 at 2/19/12 10:28 PM:
---------------------------------------------------------------
I am fine with the log messages, I just would also like to deprecate the term
"optimize" and change to "forceMerge". Thats all this issue is about. The above
log messages would then apply to forceMerge. Of course old-style optimize would
get a different message thats this is deprecated and the user is most-likely
not want to call this.
was (Author: thetaphi):
I am fine with the log messages, I just would also like to deprecate the
"term" optimize and change to forceMerge. Thats all this issue is about. The
above log messages would then apply to forceMerge. Of course optimize would get
a different message.
> 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
>
> Attachments: SOLR-3141.patch, SOLR-3141.patch
>
>
> 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]
