[
https://issues.apache.org/jira/browse/CASSANDRA-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17179112#comment-17179112
]
Alexandre Dutra commented on CASSANDRA-13951:
---------------------------------------------
Support for CASSANDRA-10786 has been released already:
# Java driver: released in 3.3.2 (see
[JAVA-1196|https://datastax-oss.atlassian.net/browse/JAVA-1196])
# Python driver: released in 3.12.0 (see
[PYTHON-808|https://datastax-oss.atlassian.net/browse/PYTHON-808])
If protocol v5 ships as is in C* 4.0 then any driver version equal to or higher
than the above will do – except for Java driver versions >= 3.10 (see below).
_However_: if CASSANDRA-15299 is merged and included in the final 4.0 GA, then
we have a totally different story to handle: we need to wait for Java driver
3.11.0 and Python driver 3.25.0. These versions are currently being prepared
and they will provide full & definitive support for both 10786 and 15299.
> Release Java and Python drivers and re-enable build.xml driver dep
> ------------------------------------------------------------------
>
> Key: CASSANDRA-13951
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13951
> Project: Cassandra
> Issue Type: Task
> Components: Build, Dependencies
> Reporter: Alex Petrov
> Assignee: Alex Petrov
> Priority: Urgent
> Fix For: 4.0, 4.x
>
>
> During [CASSANDRA-10786], driver changes were introduced that required a
> snapshot release of both drivers.
> When the stable driver version is published, we have to update the driver
> dependencies in {{lib}} and un-comment {{build.xml}} sections with
> {{java-driver}} information for correct publish of 4.0. This manipulation was
> required in order to account for the chicken-or-egg problem between Cassandra
> itself and the drivers.
> This absolutely has to be done before 4.0 & there should be no release
> without making sure right drivers are in place.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
