[ 
https://issues.apache.org/jira/browse/SOLR-5466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13924428#comment-13924428
 ] 

Erick Erickson commented on SOLR-5466:
--------------------------------------

bq: Even I found this confusing. We should use either one right?

That's what I think, but I also tried a quick hack at it (well, not so quick it 
took several hours) and tests immediately started failing so of course I messed 
something up. So I think untangling all that is best put in another JIRA so we 
don't hold up this functionality for what is essentially cleanup.

About the STATUS command. I see what you mean, it just feels overly complex. 
I'd just go for the STATUS returning the clusterstate. Here's why:
1> whatever specifics we put in there are going to require that we maintain it. 
Take this example:
STATUS&fl=name,router,replicationFactor

If I have several collections, I now have to define a syntax for what I return 
to associate the replicationFactor  with Colleciton1, Collection2, etc. Would 
it be better just to give them the cluster state and let it go at that?

I think my driving question is whether there's a need to do this that we're 
responding to or just doing it because we can. If the latter, I'm neutral to - 
on it...



> 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
>
>
> 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]

Reply via email to