[ 
https://issues.apache.org/jira/browse/SOLR-15215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17296970#comment-17296970
 ] 

David Smiley commented on SOLR-15215:
-------------------------------------

bq. would like to have the ZK netty option still available

To be clear, it will still be *available*.  It's a opt-in vs opt-out matter.  
ZK made the choice of having to opt-in but it made the dependency a normal 
dependency (you get it even if you don't opt-in).  In SolrJ, the proposal I 
make here is that clients wanting to choose Netty need to add it to their 
classpath themselves, in addition to set the system property that ZK uses to 
opt-in and/or configure SSL.

I would prefer that the base SolrJ dependency not have ZooKeeper either; we'd 
have another "solrj-zk" which would include ZK and maybe/maybe-not Netty.
And a "solrj-expressions" to hold the streaming expressions code + commons-math 
dependency, which are non-trivial.  Until any of this happens, we still only 
have one "solrj" which has too many dependencies.

> SolrJ: Remove needless Netty dependency
> ---------------------------------------
>
>                 Key: SOLR-15215
>                 URL: https://issues.apache.org/jira/browse/SOLR-15215
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: SolrJ
>            Reporter: David Smiley
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> SolrJ depends on Netty transitively via ZooKeeper.  But ZooKeeper's Netty 
> dependency should be considered optional -- you have to opt-in.
> BTW it's only needed in Solr-core because of Hadoop/HDFS which ought to move 
> to a contrib and take this dependency with it over there.



--
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

Reply via email to