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

Jason Gerlowski commented on SOLR-15542:
----------------------------------------

That makes sense to me - it'd give the parameter more consistency across 
different APIs that use it...

> Combine 'node', 'createNodeSet' parameters for ADDREPLICA API
> -------------------------------------------------------------
>
>                 Key: SOLR-15542
>                 URL: https://issues.apache.org/jira/browse/SOLR-15542
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Jason Gerlowski
>            Priority: Minor
>
> The ADDREPLICA "collection-admin" API has two parameters that are redundant 
> with one another:
> * {{node}} exists for users to explicitly specify the node to place the new 
> replica on.
> * {{createNodeSet}} lets users specify a number of nodes that Solr will then 
> choose a "winner" from.
> When {{createNodeSet}}'s value is a single node though, it behaves 
> identically to using the separate {{node}} option (AFAIK).
> If this is truly the case (and I'm not just missing something), we should 
> deprecate {{node}} and instead direct all users to use {{createNodeSet}} 
> instead. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org

Reply via email to