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 Sun, 19 Feb 2012 17:24:37 GMT


Mark Miller commented on SOLR-3141:

Lots of use of string fields that are not numerics though - the product I worked on in the
past only sorted by non numeric string fields, many times lots of them at once.

I'm coming around on this issue myself though. For the benefits, optimize is not a good name.
It calls out to be called. The abuse is clearly there, and we should probably try more to
address it than just doc.

My opinion is coming around to leave it for 3.x, change it to an expert option for 4 that
works the same, is understated, and is called forceMerge or whatever.

Big -1 to making it a no op.
> 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