[
https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211395#comment-13211395
]
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: https://issues.apache.org/jira/browse/SOLR-3141
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
