[
https://issues.apache.org/jira/browse/SOLR-11950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16354255#comment-16354255
]
Chris Ulicny commented on SOLR-11950:
-------------------------------------
Superficially seems like a simple fix. I've uploaded a patch with a test as a
starting point.
The test seemed to work, but I'm not sure if I ran it correctly or not.
> CLUSTERSTATUS shards parameter does not accept comma delimited list
> -------------------------------------------------------------------
>
> Key: SOLR-11950
> URL: https://issues.apache.org/jira/browse/SOLR-11950
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: documentation
> Affects Versions: 6.3.1, 7.2, master (8.0), 7.2.1
> Reporter: Chris Ulicny
> Priority: Minor
> Labels: collection-api
> Attachments: SOLR-11950.patch
>
>
> According to the documentation for the Collections API, the CLUSTERSTATUS
> action should accept a comma delimited list of shards if specified. However,
> when specifying a comma delimited list, it is treated as a single value
> instead of being parsed into multiple values.
> The request
> .../collections?action=CLUSTERSTATUS&collection=test_collection&shard=shard1,shard2
> yields the response:
> {"responseHeader":\{"status":400,"QTime":5},"error":\{"metadata":["error-class","org.apache.solr.common.SolrException","root-error-class","org.apache.solr.common.SolrException"],"msg":"Collection:
> test_collection shard: shard1,shard2 not found","code":400}}
> instead of locating both shard1 and shard2.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
