[
https://issues.apache.org/jira/browse/SOLR-8589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15113866#comment-15113866
]
Shawn Heisey commented on SOLR-8589:
------------------------------------
I built the branch_5x server with my patch. Then I started the cloud example,
added some collections and some aliases. WIth the CLUSTERSTATUS action, the
information about which aliases are present and what collections are used is
scattered all over the output.
I will attach a screenshot showing what you get with my patch on the LIST
action. The change will not affect most programs that consume the LIST output,
unless they are coded poorly.
> Add aliases to the LIST action results in the Collections API
> -------------------------------------------------------------
>
> Key: SOLR-8589
> URL: https://issues.apache.org/jira/browse/SOLR-8589
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Affects Versions: 5.4.1
> Reporter: Shawn Heisey
> Assignee: Shawn Heisey
> Priority: Minor
> Attachments: SOLR-8589.patch
>
>
> Although it is possible to get a list of SolrCloud aliases vi an HTTP API, it
> is not available as a typical query response, I believe it is only available
> via the http API for zookeeper.
> The results from the LIST action in the Collections API is well-situated to
> handle this. The current results are contained in a "collections" node, we
> can simply add an "aliases" node if there are any aliases defined.
--
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
