Description
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.
Attachments
Attachments
Issue Links
- depends upon
-
LUCENE-7976 Make TieredMergePolicy respect maxSegmentSizeMB and allow singleton merges of very large segments
- Closed
- is related to
-
SOLR-7666 Umbrella ticket for Angular JS post-5.2.1 issues
- Closed
-
LUCENE-7976 Make TieredMergePolicy respect maxSegmentSizeMB and allow singleton merges of very large segments
- Closed
- relates to
-
SOLR-3141 Warn in logs at Optimize (was: Deprecate OPTIMIZE command in Solr)
- Closed