[
https://issues.apache.org/jira/browse/SOLR-4388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14487737#comment-14487737
]
Shawn Heisey commented on SOLR-4388:
------------------------------------
bq. This ticket should depend upon that work.
I disagree, but not enough for a formal -1 vote. These admin UI improvements
are pretty important in my opinion. I think we should expose the Collections
API for SolrCloud collections and keep using the CoreAdmin API for cores until
the non-cloud Collections API is done. If the new API is done right, it will
be substantially similar to the existing CoreAdmin API, so the admin UI
migration should be very easy.
The CoreAdmin API is not going to disappear, at least not in any 5.x version.
It just won't be publicly documented any more, and users will be encouraged to
switch to the Collections API. Some deprecations in SolrJ are likely.
> 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]
