lucene-dev mailing list archives

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


Uwe Schindler commented on SOLR-3141:

We can even handle that:

If somebody passes optimize=true to the update request handle, we dont do anything (no optimize)
and instead print a warning message to the log saying, that optimize was disabled in Luecen
because it has no positive effect on most installations. It should also metion, that there
is a new forceMerge, but people should not call it unless they exactly know what they are

The above examples and a lot of more "howtos" on the web make the users think, they have to
optimize (after every single add). After that they complain how slow solr is. Is this really
what you want.

The FIZ Karslruhe eSciDoc projects develops the so called Europeana project, which is supposed
to index all cultural content from Europe. They are using Fedora as repository, so the above
issue was like a no-go for them to use GSearch (based on Solr). If you have so many misinformation
about optimize on the net, the most reasonable approach is to simply disable the feature in
quesion to prevent further harm.

People that rely on optimize (because they want their statistics 100% correct) will get informed
by the warning messages in the logs. For them its almost a one-line code change in their Solr
client. If they dont do it, they will also not be disaapointed, because: 

bq. There is less of a slowdown - but it's certainly still there

So they would in most cases not even recognizing because new versions of solr will bring other
> 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