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

Ralph Tice commented on SOLR-6422:
----------------------------------

Linking original Jira for historical reference, didn't seem to get much 
dialogue at that time.

> DELETEREPLICA exposes an inconsistent param REPLICA_PROP
> --------------------------------------------------------
>
>                 Key: SOLR-6422
>                 URL: https://issues.apache.org/jira/browse/SOLR-6422
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>    Affects Versions: 4.10
>         Environment: Ubuntu 14.04
>            Reporter: Ralph Tice
>            Priority: Minor
>
> DELETEREPLICA asks for the ZK "shard id" (core_node_###) instead of the same 
> syntax as createNodeSet?  I can't recall any other instance in which the ZK 
> "shard id" is exposed via query parameter and I've only ever seen it in 
> clusterstate.json / CLUSTERSTATUS calls.
> For ease of use I humbly suggest that the API be amended to take the same 
> parameters are ADDREPLICA and use either base_url or core_node_name.
> Specifically, instead of REPLICA_PROP here 
> https://github.com/apache/lucene-solr/blob/branch_4x/solr/solrj/src/java/org/apache/solr/common/cloud/ZkStateReader.java#L64
> it would be more consistent to request a query param of the form: 
> https://github.com/apache/lucene-solr/blob/branch_4x/solr/solrj/src/java/org/apache/solr/common/cloud/ZkStateReader.java#L58
>  
> or: 
> https://github.com/apache/lucene-solr/blob/branch_4x/solr/solrj/src/java/org/apache/solr/common/cloud/ZkStateReader.java#L56
> Also it appears DELETEREPLICA is missing from 
> https://github.com/apache/lucene-solr/blob/branch_4x/solr/solrj/src/java/org/apache/solr/common/params/CollectionParams.java



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