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 16:22:46 GMT


Yonik Seeley commented on SOLR-3141:

bq. With Lucene 3.x there is really no slowdown at all caused by multiple segments

There is less of a slowdown - but it's certainly still there.  Whether it matters or not will
depend on the exact use-cases.

bq. Solr has some problems with facetting, but people should use per-segment facetting and
not optimize

No... people should do whatever suits their usecase best.

Some very well informed users of Solr still optimize.  They change their index infrequently
(like once a day), and have determined that the performance increases they see by optimizing
make it worth it for them.

> 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