[
https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679641#comment-13679641
]
Shawn Heisey commented on SOLR-3141:
------------------------------------
Before I read HossMan's proposals thoroughly, I had these thoughts:
---
I would support removing the optimize button from the GUI, or at least removing
it from the Overview page. Keeping it on the CoreAdmin page would not be a bad
thing, optionally with at least one confirmation dialog that reminds the user
that optimization is not normally required.
Deprecating "optimize" from the GUI and the API in favor of forceMerge would
not make me upset either, as long as it continued to work through all 4.x
versions. Based on what happened with waitFlush and the PHP Solr API packages
after the 4.0 release, this is a dangerous path, but if we kept optimize around
until 6.0, perhaps it might be OK.
---
After reading the proposals, I think there might be a small amount of merit in
my ideas, but his ideas are safer.
> 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: 4.4
>
> 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
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]
