lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-3141) Deprecate OPTIMIZE command in Solr
Date Sun, 19 Feb 2012 19:38:42 GMT


Robert Muir commented on SOLR-3141:

A warning message seems over the top.

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.

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.

+1, I think those are good improvements.

> Deprecate OPTIMIZE command in Solr
> ----------------------------------
>                 Key: SOLR-3141
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message