[
https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211488#comment-13211488
]
Uwe Schindler commented on SOLR-3141:
-------------------------------------
Robert: I would also agree with this. If others dont want to make optimize() a
noop, I would agree to make a serious log.warn() or even better log.fatal() out
of it saying that it's a bad idea in most cases. And that it's deprecated
(deprecation by log printing, funny). People who call optimize or forceMerge
after ech single document will have a log filled with warning messages, this
should make them look into it.
In my opinion expungeDeletes and forceMerge should always print a warning-like
message to the log, saying that it's doing something heavy and
resource-wasteful. Optimize aditionally also say that its deprecated.
> 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]
