[
https://issues.apache.org/jira/browse/SOLR-7733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14608661#comment-14608661
]
Hoss Man commented on SOLR-7733:
--------------------------------
Linking related SOLR-3141 where there was much discussion about terminology and
backcompat and educating users and sensible default behavior.
(i have no comment or opinion about anything expressed in this issue so far --
i have not read most details in this issue so far, i'm just linking the issues
so all the relevant details are connected for folks who do have opinions and
are willing to follow through on them)
> 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: UI
> Affects Versions: 5.3, Trunk
> Reporter: Erick Erickson
> Priority: Minor
> Attachments: 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.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
