lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-3141) Deprecate OPTIMIZE command in Solr
Date Mon, 20 Feb 2012 15:21:34 GMT


Mark Miller commented on SOLR-3141:

I think when it comes to API breaks, trying to say we can't fix this one because we can't
fix every old little thing doesn't jive. The name is clearly not a good one, and the call
will not be the right move for most people that upgrade to 4. Having to rethink that will
be doing 99% of users a favor. Changing the name will be doing all future users a favor. 

I think 4 should be about getting things right without clinging to old baggage. We are not
talking about the update or request apis here. We are talking about a very expensive, very
poorly named, very little little returns API call that is certainly over used (and much of
the over use is not going to end up on google).

Making those that upgrade rethink optimize seems like just what the Dr ordered - we can add
it to the release announce, the release notes, etc. Even though I know exactly what this does,
even though i know the price/benefits - I still want to call this thing at least once a week.
It's a terrible name at this point. Why are we stuck with terrible?
> 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
>         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:!default.jspa
For more information on JIRA, see:


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

View raw message