[
https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211310#comment-13211310
]
Jan Høydahl commented on SOLR-3141:
-----------------------------------
I propose OPTIMIZE should still work in 3.x but be deprecated and yell about it
in the logs. The most straight-forward is perhaps to add a new forceMerge
command to replace the old one. Then from 4.0 the old optimize command would be
a NOP command.
Reasoning behind this is that <optimize/> causes a lot of people trouble in
Solr today because it's over-used due to its luring name. I don't think anyone
will miss it once it's gone, and those who really need it can start using
<forceMerge/> which is a better name anyhow.
> 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]
