[
https://issues.apache.org/jira/browse/SOLR-5466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13917121#comment-13917121
]
Erick Erickson commented on SOLR-5466:
--------------------------------------
OK, I'm officially confused. What are the guidelines for collection actions
going through the Overseer? The LISTCOLLECTIONS action does, but the STATUS
command doesn't, it's handled locally in CollectionsHandler. What's the right
thing to do here?
And if the answer is to go through the Overseer for all collection actions, can
we prevent short-circuiting like this?
Thanks
> 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
>
>
> 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.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
