[jira] [Created] (SOLR-11803) Remove all traces of "optimize" from Solr and replice with "forceMerge"

["Erick Erickson (JIRA)" <ji...@apache.org>]

Erick Erickson created SOLR-11803:
-------------------------------------

             Summary: Remove all traces of "optimize" from Solr and replice with "forceMerge"
                 Key: SOLR-11803
                 URL: https://issues.apache.org/jira/browse/SOLR-11803
             Project: Solr
          Issue Type: Improvement
      Security Level: Public (Default Security Level. Issues are Public)
            Reporter: Erick Erickson
            Priority: Minor


Umbrella issue for removing optimize from Solr.

This has been kicked around for quite some time. It turns out that there are a number of places all this is baked in to code. Here are the places hinted at by just looking at the reference guide:

suggester has "buildOnOptimize".
DIH has optimize.
postOptimize hook
IgnoreCommitOptimizeUpdateProcessorFactory
ignoreOptimizeOnly
buildOnOptimize
And what about JMX stats? UPDATE.updateHandler.optimizes

Then there are about a zillion places in the code that use optimize, I'm not sure how many of those would need to change. Lots of tests for instance have: "assertU(optimize());"

The first step would be to deprecate public static String OPTIMIZE = "optimize" in  UpdateParams, add FORCEMERGE and proceed from there.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org