[ https://issues.apache.org/jira/browse/SOLR-7176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Per Steffensen updated SOLR-7176: --------------------------------- Attachment: SOLR-7176.patch New patch bq. I would prefer not to retry automatically Adding "Try again" to error-msg from ZkCLI if KeeperException.BadVersionException (to hint the user that it will probably go well if he just tries again). Besides that * Also "// Don't update ZK unless absolutely necessary" in the remove-case * Sharing constants instead of introducing new similar ones. Because IMHO we shouldnt keep adding the same constants again and again, but more important: If HTTP is {{/admin/collections?action=CLUSTERPROP&name=<prop-name>&val=<prop-value>}}, then the command-line should be {{zkcli.sh … -cmd CLUSTERPROP -name <prop-name> -val <prop-value>}}, AND if the HTTP ever changes (e.g. using “clusterprop.set” instead of “CLUSTERPROP”) so should the command-line * Adding test of remove * Closing ZkStateReader in CollectionsHandler, ZkCLI and ZkCLITest > allow zkcli to modify JSON > -------------------------- > > Key: SOLR-7176 > URL: https://issues.apache.org/jira/browse/SOLR-7176 > Project: Solr > Issue Type: New Feature > Reporter: Yonik Seeley > Assignee: Noble Paul > Priority: Minor > Attachments: SOLR-7176.patch, SOLR-7176.patch, SOLR-7176.patch, > SOLR-7176.patch > > > To enable SSL, we have instructions like the following: > {code} > server/scripts/cloud-scripts/zkcli.sh -zkhost localhost:2181 -cmd put > /clusterprops.json '{"urlScheme":"https"}' > {code} > Overwriting the value won't work well when we have more properties to put in > clusterprops. We should be able to change individual values or perhaps merge > values. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org