[
https://issues.apache.org/jira/browse/SOLR-8589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114037#comment-15114037
]
Shawn Heisey commented on SOLR-8589:
------------------------------------
I've discovered that the CREATEALIAS action does not validate whether the
target collections actually exist.
I can understand a need to create an alias before the collection exists ...
what I propose is that the action should normally validate, but have an option
to toggle the validation. Because of the potential for a backward
compatibility break with existing user code, changing the default behavior
would need to happen in 6.0.
> 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, solr-8589-new-list-details-aliases.png
>
>
> 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
