[
https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211359#comment-13211359
]
Uwe Schindler edited comment on SOLR-3141 at 2/19/12 3:39 PM:
--------------------------------------------------------------
Yonik: I disagree here:
One problem is e.g., DIH it optimizes by default which is the stupidest thing
it could do on every incremental update (see SOLR-3142)
If you disagree, I would simple (as suggested before by me) to make optimize a
no-op in Solr. Very easy and hurts nobody, but prevents people from doing the
wrong thing.
was (Author: thetaphi):
Yonik: I disagree here:
The biggest mess is DIH - it optimizes by default which is the stupidest thing
it could do
If you disagree, I would simple (as suggested before by me) to make optimize a
no-op in Solr. Very easy and hurts nobody, but prevents people from doing the
wronng thing.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
