[
https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211611#comment-13211611
]
Uwe Schindler commented on SOLR-3141:
-------------------------------------
bq. I doubt it. An dhow did they find the command in the first place?
By copying one of those "shiny" code examples I posted!
Just to come back to programmers that should have read the documentation, but
in fact they did not. The best example from the above list is
[http://drupal.org/node/292662]. Drupal is one of the most often used CMS
systems (I just mention that your company also uses it for their home page) and
its installed on thousands of servers. And this tool also contains a full text
search engine (maybe your company is not using that one), but this one called
commit and optimize after every update (until they fixed it). Isn't that funny.
In fact Drupal users are a huuuuuuuuuuuuuuuuuuuuuuuuuuuuge majority that dont
know what their system is doing under the hood and largely depend on the fact
that PHP programmers like the Drupal ones dont call optimize just because it's
called optimize.
> 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
>
> Attachments: SOLR-3141.patch, SOLR-3141.patch
>
>
> 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]
