lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-4316) Admin UI - SolrCloud - extend core options to collections
Date Fri, 15 Feb 2013 17:09:12 GMT

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

Mark Miller commented on SOLR-4316:
-----------------------------------

It's how most distributed systems work. You hit one node, it queries your cluster by default
- not just that one node.
                
> 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
>             Fix For: 4.2, 5.0
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message