As a follow-up, the drivers team at DataStax has just released Java drivers 3.9.0 and 4.6.0. You can read more from the drivers mailing list links below:
3.9.0: https://groups.google.com/a/lists.datastax.com/forum/#!msg/java-driver-user/NCqlbiGp62E/nm26BmeRAwAJ 4.6.0: https://groups.google.com/a/lists.datastax.com/forum/#!msg/java-driver-user/jub63zTzOBY/R9XGoCCTAwAJ Thanks, Erik Merkle (on behalf of the drivers team) On Thu, Apr 9, 2020 at 9:30 AM Alexandre Dutra <alexandre.du...@datastax.com> wrote: > Hi, > > The drivers team at DataStax is joining the effort towards releasing > Cassandra 4.0 by > supporting all its new features in recent driver releases. Below is an > update on our > status, more to come as we progress: > > * Python driver 3.23.0 was released on April 6th and ships with > support for peers_v2 and > transient replication; protocol v5 is fully implemented, with the > exception of > CASSANDRA-14664 (now-in-seconds) [1]. > > * Java drivers 3.9.0 and 4.6.0 will be released in the next few weeks. > They will include > support for missing features (transient replication and > now-in-seconds), effectively > providing complete support for protocol v5 in its current state. To > make it as easy as > possible for users to adopt C* 4.0, we decided to release both major > branches of the Java > driver, including 3.x, even if this branch is now in maintenance mode. > > * C# driver 3.15.0 is planned for sometime in May; it should include > support for peers_v2, > transient replication, and a fairly comprehensive set of protocol v5 > features. > > * Other drivers may follow this year. > > Note that until CASSANDRA-14973 [2] is merged, all drivers consider > protocol v5 as beta. > This means that users need to explicitly allow usage of beta protocols > in their drivers > before they can connect with v5. > > Also note that CASSANDRA-15299 [3] is expected to change protocol v5 > radically. Currently, > drivers do not use any form of checksumming technique when connecting > with v5. If anyone > is able to bump that ticket in priority we will certainly appreciate > it on the drivers > side so we can complete the implementation. > > If there is anything else that we could do to help in getting Cassandra > 4.0 out, > please let us know. > > Thanks, > > Alexandre Dutra > > [1] https://issues.apache.org/jira/browse/CASSANDRA-14664 > [2] https://issues.apache.org/jira/browse/CASSANDRA-14973 > [3] https://issues.apache.org/jira/browse/CASSANDRA-15299 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > > -- Erik Merkle e. erik.mer...@datastax.com w. www.datastax.com
