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

Shalin Shekhar Mangar commented on SOLR-4316:
---------------------------------------------

[~steffkes] suggested that we combine the two selection boxes for collection 
and local cores into one but group them together just as how the Analysis page 
shows a single selection box with field names and field types.

I have gone back and forth on this. It isn't hard to implement because it takes 
just a "optgroup" html element to group both types together. But after a lot of 
thought I am leaning towards keeping these two separate because:
# Imagine "collection1" which is both a collection as well as a core name. Once 
the user has already selected one of them there is no way to indicate what has 
been selected (except the fact that different options show depending on what's 
selected)
# The Analysis page shows field types and names together but they're also 
functionally equivalent with respect to that page. However, different functions 
apply on collections and cores.

The cons of having two selection boxes is that it takes more screen space and 
we turn on scrolling only when the viewport size is smaller (or it is resized 
to be smaller).

> Admin UI - SolrCloud - extend core options to collections
> ---------------------------------------------------------
>
>                 Key: SOLR-4316
>                 URL: https://issues.apache.org/jira/browse/SOLR-4316
>             Project: Solr
>          Issue Type: Improvement
>          Components: web gui
>    Affects Versions: 4.1
>            Reporter: Shawn Heisey
>            Assignee: Shalin Shekhar Mangar
>             Fix For: 4.9, 5.0
>
>         Attachments: SOLR-4316.patch, solrcloud-admin-ui-menu.png
>
>
> There are a number of sections available when you are looking at a core in 
> the UI - Ping, Query, Schema, Config, Replication, Analysis, Schema Browser, 
> Plugins / Stats, and Dataimport are the ones that I can see.
> A list of collections should be available, with as many of those options that 
> can apply to a collection,  If options specific to collections/SolrCloud can 
> be implemented, those should be there too.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to