[ https://issues.apache.org/jira/browse/SOLR-9743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16278582#comment-16278582 ]
Christine Poerschke commented on SOLR-9743: ------------------------------------------- Hi, not quite sure if this is the best place to mention it and/or if replying to the commit message on the dev list would be clearer. Anyhow, I just encountered a strange cherry-picking conflict for {{solr/CHANGES.txt}} on SOLR-9137 and from quick look around it seems that the above https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=c62d538 inadvertently removed some solr/CHANGES.txt chunks and the follow-on https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=093f6c2 restored some but not all of the chunks and further chunks might need to be restored. > An UTILIZENODE command > ---------------------- > > Key: SOLR-9743 > URL: https://issues.apache.org/jira/browse/SOLR-9743 > Project: Solr > Issue Type: Sub-task > Security Level: Public(Default Security Level. Issues are Public) > Reporter: Noble Paul > Assignee: Noble Paul > Fix For: 7.2 > > > The command would accept one or more nodes and create appropriate replicas > based on some strategy. > The params are > *node: (required && multi-valued) : The nodes to be deployed > * collection: (optional) The collection to which the node should be added > to. if this parameter is not passed, try to assign to all collections > example: > {code} > action=UTILIZENODE&collection=gettingstarted > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org