[ 
https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211506#comment-13211506
 ] 

Robert Muir commented on SOLR-3141:
-----------------------------------

{quote}
A warning message seems over the top.
{quote}

I don't think a warning message for a deprecated command is over the top,
how else will people know to switch to 'forceMerge' (in the case they really 
need it).

We already log warning messages if people use e.g. deprecated analyzers or 
other things,
I'm just suggesting we deprecate the trappy name like anything else would be 
deprecated.
It seems worse to me to silently deprecate something.

By the way: I think it would also be nice if the forceMerge required _n_ as a 
parameter, 
rather than defaulting to 1.

{quote}
Here's the current wiki text (I just modified it to suggest what "infrequently" 
might mean... i.e. nightly, not on the minute or something), added the term 
"very expensive" and bolded the "entire" to draw attention to it.
{quote}

+1, I think those are good improvements.

                
> 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]

Reply via email to