[
https://issues.apache.org/jira/browse/SOLR-8589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15448491#comment-15448491
]
Jan Høydahl commented on SOLR-8589:
-----------------------------------
bq. If we do this, do you think there is going to be confusion between when to
use CollectionAdminParams.COLLECTION and CollectionAdminParams.COLLECTIONS?
That's the only potential downside that I can see.
Thinking about it, perhaps it is better to skip this detailed control of what
to list. Keep things simple. We add a section to the LIST XML response. It is
generally useful, it is not huge in size, and no real benefit to be able to
turn it on or off imo.
{quote}
bq. Also, I think we should return aliases by default.
I don't know if there is anybody out there that has some kind of monitoring
script set up to parse the result of LIST, and in general I try to be super
conservative about changing APIs. Maybe we default to returning them in 7.0,
and not returning them in 6.x? That sounds like a fair compromise to me.
{quote}
This is XML, and we *add* a new XML node, not changing anything of the
existing. Any XML parser used to retrieve the {{<arr name="collections">}}
would still work exactly as before. So even if someones script breaks, that
will still not be a bug on our parts, this is not a back-compat break.
I can take a stab at simplifying the patch :)
> 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.patch, SOLR-8589.patch,
> 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: [email protected]
For additional commands, e-mail: [email protected]
