lucene-dev mailing list archives

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


Yonik Seeley commented on SOLR-3141:

And if we did change, naive users would be:
 "oh, optimize doesn't work any more..." (looks up what it's been changed to) "ok, changed
to forceMerge."

After forceMerge is out there for a while, it would have the same problem as optimize.  Someone
tries it, their queries run faster, and it gets passed along as something to try to speed
things up (and it is in the right scenario).  The correct path here is to document it correctly,
and get rid of any bad examples in our documentation.

Someone can add a big fat message at the top of CHANGES explaining the cost of optimize and
the fact that it's often less necessary than it was in the past if they want.
> 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