[
https://issues.apache.org/jira/browse/SOLR-5466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13945535#comment-13945535
]
Shalin Shekhar Mangar commented on SOLR-5466:
---------------------------------------------
bq. And, I started to untangle the fact that we have all the strings in
OverseerCollectionProcessor, but also have a nice CollectionAction enum. And
the commands are intermingled with parameters, it all seems rather confusing.
Does it make sense to use the enum rather than the strings? Or somehow
associate the two? Probably something for another JIRA though
Yeah, it is a mess. I'll open an issue to clean this up.
[~varunthacker] - I like the fl syntax but I think it may be hard to maintain.
At least this way all properties inside cluster state are automatically
returned. We can always add the filtering feature later if we want.
> 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]
