[
https://issues.apache.org/jira/browse/SOLR-7176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14498684#comment-14498684
]
Hrishikesh Gadre commented on SOLR-7176:
----------------------------------------
[~andyetitmoves] [~nobel.paul][[email protected]][~steff1193]
I think the problem with the latest proposal (from Nobel) is that the user is
expected to download the clusterprops.json file and update it correctly.
Shouldn't this logic be part of Solr itself (to ensure backward compatibility
w.r.t. schema changes etc.) ?
How about just adding a separate class in Solr which would provide this
functionality viz.
- Download the ZK config
- Update it correctly
- Upload the ZK config
We can potentially refactor the current collections API implementation to use
this class (so as to avoid code duplication). We can optionally provide a
separate script to invoke this class (or leave it for consumers to implement).
This will address the concerns with respect to adding this functionality to
zkcli.sh.
Thoughts?
> 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
> Priority: Minor
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
