lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (Updated) (JIRA)" <>
Subject [jira] [Updated] (SOLR-3141) Deprecate OPTIMIZE command in Solr
Date Sun, 19 Feb 2012 15:40:34 GMT


Uwe Schindler updated SOLR-3141:

    Comment: was deleted

(was: I am just saying that DIH is wrong to *default* to optimize. It has nothing to do with
the naming. I would also argue if DIH would call it forceMerge(1) and default to do it! This
slows down incremental DIH updates by O(n^2).

bq. Are you saying that committers don't know the cost of optimize?

The people who invented DIH were no committers at the time they wrote it. And those had really
no idea, sorry. We all know that DIH code was and is not the best the software industry provides.
If we would have a better alternative without locale, threading and unicode bugs, I would
svn rm.)
> 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