[
https://issues.apache.org/jira/browse/SOLR-7733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16215253#comment-16215253
]
Yonik Seeley commented on SOLR-7733:
------------------------------------
bq. Just had another realization: Before committing this, I'll change the ref
guide and change all the "optimize" to "forceMerge".
Generic mentions perhaps? The API itself should continue to be documented.
I added warnings in the past to the old wiki about expensive rewriting of the
entire index, so we should also add something about lack of natural merging
away of deletes.
> remove/rename "optimize" references in the UI.
> ----------------------------------------------
>
> Key: SOLR-7733
> URL: https://issues.apache.org/jira/browse/SOLR-7733
> Project: Solr
> Issue Type: Improvement
> Components: Admin UI
> Affects Versions: 5.3, 6.0
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Priority: Minor
> Attachments: SOLR-7733.patch, SOLR-7733.patch
>
>
> Since optimizing indexes is kind of a special circumstance thing, what do we
> think about removing (or renaming) optimize-related stuff on the core admin
> and core overview pages? The "optimize" button is already gone from the core
> admin screen (was this intentional?).
> My personal feeling is that we should remove this entirely as it's too easy
> to think "Of course I want my index optimized" and "look, this screen says my
> index isn't optimized, that must mean I should optimize it".
> The core admin screen and the core overview page both have an "optimized"
> checkmark, I propose just removing it from the "overview" page and on the
> "core admin" page changing it to "Segment Count #". NOTE: the "overview" page
> already has a "Segment Count" entry.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
