lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Upayavira (JIRA)" <>
Subject [jira] [Commented] (SOLR-4316) Admin UI - SolrCloud - extend core options to collections
Date Mon, 24 Aug 2015 16:01:46 GMT


Upayavira commented on SOLR-4316:

My take is ever so slightly different - I'd like to do the absolute minimum to make it worth
people's time to switch over to the new one.

To my mind, that is this ticket and SOLR-4388. If we have both of these in place as new features,
and have covered SOLR-7856 then I'd be happy to proceed to make it default. Still aiming for
all that for 5.4.

i.e. if we're gonna make things worse for people (some lingering bugs) we might as well also
make it a little better (new features).

> Admin UI - SolrCloud - extend core options to collections
> ---------------------------------------------------------
>                 Key: SOLR-4316
>                 URL:
>             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, SOLR-4316.patch, collections menu open.png, cores
menu open.png, solrcloud-admin-ui-menu.png, two-selectors.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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message