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

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

bq. Users of low-res displays might appreciate having one dropdown with both 
collections and cores, similar to what we have on the schema browser for 
Fields, DynamicFields, and Types. 

I know Shawn but right now you can have a collection and a core named the same 
e.g. "collection1". How would you choose one over the other? I think, 
eventually, we want to move away from the local core concept in the UI and 
navigate to individual cores from a collection view but I want to take small 
baby steps right now.

That reminds me that the current menu has a fixed height I guess because on 
lower resolutions, one cannot scroll to the bottom of the menu. Instead, part 
of the menu is just cut off below the viewport and becomes unreachable.  This 
is something that we should fix anyways. This is especially a problem during 
workshop/demos because the projectors have low resolution.

> 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: 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