[
https://issues.apache.org/jira/browse/SOLR-4316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653367#comment-14653367
]
Upayavira commented on SOLR-4316:
---------------------------------
I'm inclined to use the latter approach. Let each page decide whether the thing
after the #/ is a core name or a collection name. We do that already in
standard Solr URLs.
Either we let each page decide, if the page only works with cores or with
collections, or we check for a collection first, and if we don't find one, we
fall back to a core.
The schema browser really is the only tab we have at the moment that is
ambiguous - the schema is shared across a collection, but the term info is core
specific. In my first pass I'll make it core specific. Later we could have it
on both, with a flag telling us which, and if you click "show term info" on the
collections page, it'll give you a list of replicas to try it on.
> 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: Upayavira
> Fix For: 4.9, Trunk
>
> 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.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
