[ 
https://issues.apache.org/jira/browse/SOLR-7733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14605589#comment-14605589
 ] 

Yonik Seeley commented on SOLR-7733:
------------------------------------

This could just cause confusion about "where did optimize go?"
The issue seems largely one of education.   Optimize (or forceMerge) is a valid 
operation and one that can be called for in certain circumstances.  Users need 
to understand the cost, so they can make the call.

I agree we should get rid of any notion/mention of "unoptimized" though, 
including the colors Shawn mentions.

One alternative to straight out removal is to educate the user right next to 
the button: 
"This optional operation is very expensive and not normally necessary.  It will 
rewrite the entire index into a single segment"

OR if we have the index size available:

"This optional operation is very expensive and not normally necessary.  It will 
rewrite all NNN MB of the index into a single segment"


> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to