[
https://issues.apache.org/jira/browse/SOLR-14070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16999139#comment-16999139
]
Jason Gerlowski commented on SOLR-14070:
----------------------------------------
bq. This is inherently insecure.
Can you elaborate a bit on this please? AFAIK clusterstate, security.json,
etc. information is going to be in ZooKeeper with the same protections,
regardless of how SolrJ finds the shape/status of a particular cluster. I
can't see how deprecating this constructor will make that information any more
or less protected.
> Deprecate CloudSolrClient's ZKHost constructor
> ----------------------------------------------
>
> Key: SOLR-14070
> URL: https://issues.apache.org/jira/browse/SOLR-14070
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Ishan Chattopadhyaya
> Priority: Major
>
> CloudSolrClient can be used by pointing it to a ZK cluster. This is
> inherently insecure.
> CSC can already be used in all the same ways by pointing it to a Solr cluster.
> Proposing to add a deprecation notice to the following constructor to the
> CloudSolrClient#Builder:
> {code}
> public Builder(List<String> zkHosts, Optional<String> zkChroot)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
