lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (Commented) (JIRA) <>
Subject [jira] [Commented] (SOLR-3141) Deprecate OPTIMIZE command in Solr
Date Mon, 20 Feb 2012 13:02:34 GMT


Jan Høydahl commented on SOLR-3141:

I think 4.0 is a good train in which to do this rename, when people will anyway take a thorough
new look at all the changes, and most will hopefully discover that they do *not* need forceMerge
even if they used optimize before. And I agree, in 4.x, "optimize" should not be a silent
NOOP, but instead yell loudly in the logs.

Perhaps an official migration guide on the CMS would be helpful too when 4.0 hits the road.
Such a guide would be more in-depth than the upgrading notes in CHANGES. We could have a paragraph
about optimize/forceMerge, and another paragraph about softCommit/commitWithin as preferred
to explicit commit, which is also a huge mistake many people do, they do over-committing!
> 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