[
https://issues.apache.org/jira/browse/SOLR-4388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14487230#comment-14487230
]
Upayavira commented on SOLR-4388:
---------------------------------
This is the most obvious next step once the AngularJS Admin UI is completed,
although, I wonder whether we need the collections API to work in non-cloud
mode, and then build a UI around that.
(there are two more panes to do on the AngularJS UI, both of which I am half
way through)
> Admin UI - SolrCloud - expose Collections API
> ---------------------------------------------
>
> Key: SOLR-4388
> URL: https://issues.apache.org/jira/browse/SOLR-4388
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.1
> Reporter: Shawn Heisey
> Fix For: Trunk, 5.2
>
>
> The CoreAdmin API is fairly well represented in the UI. When SolrCloud is
> enabled, the Collections API for SolrCloud needs similar treatment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
