[
https://issues.apache.org/jira/browse/CASSANDRA-7692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14147442#comment-14147442
]
Robert Stupp commented on CASSANDRA-7692:
-----------------------------------------
One solution would be to exclude the Java driver from $CASSANDRA_HOME/lib for
the tools - e.g. introduce some "C* daemon internal lib dir".
I know [~norman] is working on [netty update
(JAVA-352)|https://datastax-oss.atlassian.net/browse/JAVA-352] in the Java
driver.
As soon as we use the Java driver in C* daemon classpath it might break
embedded uses of C*.
IMO a proper solution would be to split the Java driver into separate modules
and only use the "data related" part of it for CASSANDRA-7563.
[~slebresne], [~iamaleksey] any thoughts?
> Upgrade Cassandra Java Driver to 2.1
> ------------------------------------
>
> Key: CASSANDRA-7692
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7692
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Robert Stupp
> Assignee: Robert Stupp
> Fix For: 3.0
>
> Attachments: 7692-2.1.txt, 7692-3.0.txt, 7692-3.0v2.txt
>
>
> UDFs (CASSANDRA-7563) requires Java Driver that supports User Types and new
> collection features (at least Java Driver 2.1).
> May also be handled separately if e.g. Hadoop stuff requires this (follow-up
> to CASSANDRA-7618).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
