[ https://issues.apache.org/jira/browse/SOLR-15342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17585096#comment-17585096 ]
David Smiley commented on SOLR-15342: ------------------------------------- When we release Solr 9.1 and craft the release highlights; it's going to really important to spell out the potential need for solrj-zookeeper. Lots of users are going to add this. I'll copy some bits added in the ref guide solr-upgrade-notes.adoc: {quote}SolrJ is beginning to be split up. If you use ZooKeeper coordinates to create a `CloudSolrClient`, you will need to add a dependency on `solrj-zookeeper`. Instead, consider migrating to use of specifying a list of Solr URLs in the client's builder. Not only does this reduce dependencies, but it improves security by being able to limit ZooKeeper access. {quote} In retrospect, `solr-solrj-zookeeper` is actually the artifact ID (the extra `solr-` up front). > Separate out a SolrJ-Zookeeper module > ------------------------------------- > > Key: SOLR-15342 > URL: https://issues.apache.org/jira/browse/SOLR-15342 > Project: Solr > Issue Type: Sub-task > Components: SolrJ > Reporter: David Smiley > Assignee: David Smiley > Priority: Major > Fix For: 9.1 > > Time Spent: 10h 50m > Remaining Estimate: 0h > > Let's create a new "SolrJ-Zookeeper" module by refactoring out the ZooKeeper > related code out of the existing SolrJ module. This allows clients that > don't want to talk to ZooKeeper to use the SolrJ module without transitive > dependencies for ZooKeeper or Netty (Netty is used by ZK for SSL). -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org