[
https://issues.apache.org/jira/browse/SOLR-5466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-5466:
----------------------------------------
Attachment: SOLR-5466.patch
# Added \_route\_ parameter which can be used in place of _shard_. The given
route key will be used to determine the shard info to be returned. This will be
useful to know which shard a given route key resolves to.
# Fixed TestCollectionAPI which was incorrectly expecting collections to be
returned in a certain order.
I'm going to add shard address in the response. Most clients would like to know
the base url of the shard. It is not easy to know that info from the node_name,
core_name etc returned by the cluster state. I'll also add cluster properties,
aliases and roles.
> Add List Collections functionality to Collections API
> -----------------------------------------------------
>
> Key: SOLR-5466
> URL: https://issues.apache.org/jira/browse/SOLR-5466
> Project: Solr
> Issue Type: Sub-task
> Components: scripts and tools, SolrCloud
> Environment: All
> Reporter: Dave Seltzer
> Assignee: Shalin Shekhar Mangar
> Priority: Minor
> Labels: api, collections, rest
> Attachments: SOLR-5466.patch, SOLR-5466.patch, SOLR-5466.patch,
> SOLR-5466.patch, SOLR-5466.patch, SOLR-5466.patch
>
>
> The collections API lets you add, delete and modify existing collections. At
> the moment the API does not let you get a list of current collections or view
> information about a specific collection.
> The workaround is the use the Zookeeper API to get the list. This makes the
> Collections API harder to work with.
> Adding an action=LIST would significantly improve the function of this API.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
