[
https://issues.apache.org/jira/browse/SOLR-4388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14487324#comment-14487324
]
Varun Thacker commented on SOLR-4388:
-------------------------------------
Maybe it should expose it as one? Like how the start script does with the
'create' option. If it's standalone Solr then we make core admin calls. If it's
SolrCloud then Collection API calls will be made.
As discussed here http://markmail.org/thread/i4ynycr5fsqc275j we want to stop
exposing the core admin apis. So if we do it we'll be masking it from the UI
and when that is implemented make all calls to the collection api.
Any opinions on whether this is a good idea?
> 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: [email protected]
For additional commands, e-mail: [email protected]
