[
https://issues.apache.org/jira/browse/SOLR-14070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17939682#comment-17939682
]
David Smiley commented on SOLR-14070:
-------------------------------------
I suppose the scope of this issue is strictly deprecation. But ideally we'd
also create some additional Jira issues and/or some TODO in the code to help
the ultimate transition along.
Within Solr (the server, meaning), and many of Solr's tests, the ZK option is
going to be used still. I don't see "RunSampleTool" but I do see
"RunExampleTool" which is CLI, so shouldn't be talking to ZK (unless the "tool"
was ZK oriented; this isn't). RunExampleTool is literally starting Solr
itself, and it needs ZK for that, so don't touch that. KafkaCrossDCConsumer
ought to be updated to take a Solr host connection string as an alternative
option to the ZK one.
> Deprecate CloudSolrClient's ZKHost constructor
> ----------------------------------------------
>
> Key: SOLR-14070
> URL: https://issues.apache.org/jira/browse/SOLR-14070
> Project: Solr
> Issue Type: Improvement
> Reporter: Ishan Chattopadhyaya
> Priority: Major
> Fix For: main (10.0)
>
>
> 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.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
