lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Upayavira (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-4316) Admin UI - SolrCloud - extend core options to collections
Date Mon, 03 Aug 2015 19:59:05 GMT

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

Upayavira commented on SOLR-4316:
---------------------------------

I started playing with this yesterday. I started mocking up Shalin's patch in Angular. The
patch as he showed it in the screenshot is pretty easy - two dropdowns, and submenus below
those dropdowns. 

The issue I stumbled upon was actually URL structure rather than the dropdowns.

We have:
http://localhost:8983/solr/#/~xyz     for a page 'xyz' that is not core specific.
http://localhost:8983/solr/#/core1/tab1  for a page that is specific to a particular core.

How do we represent, in a URL, a link to a page that is specific to a particular collection?

Do we need something like:

http://localhost:8983/solr/#/@collection1/tab1  (using some marker (e.g. @) to signify a collection

Or do we just say that, for example:

http://localhost:8983/solr/#/assets/analysis  <-- is a collection page, because analysis
is collection specific
http://localhost:8983/solr/#/assets/segments <-- is a core page, because segment info is
core specific

Thoughts?

> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message