Hi all, I and Bohdan Syrik have completed a round of testing of gocql v2.1.0-tentative.
Cadence compatibility All unit tests have passed successfully and most live Cassandra smoke tests. The only exception is the MapScan behavior, which differs from the legacy driver; however, this behavior seems to predate the changes between 2.0.0 and 2.1.0 and doesn't seem to be introduced in this release. That said, I only upgraded Cadence as part of this validation so further investigation is needed to confirm whether the behavior is entirely on gocql v2. I will create an issue for this. Testcontainers-based integration testing I also revived and rebased an older branch (CCM replacment). All tests passed except for Cassandra 5.0.3 with Protocol v4 and compression enabled (Snappy or LZ4), where tests consistently hang or fail. All other tested configurations completed successfully. I have not reduced that to a single isolated test yet, so at the moment I would treat it as a known issue in the legacy compressed protocol 4 path rather than a release blocker for the broader driver. Here's link to the PR with matrix https://github.com/apache/cassandra-gocql-driver/pull/1780 Based on current evidence, my vote is +1 non-binding and tentative (pun intended). I do not see any clear regressions in 2.1.0-tentative compared to 2.0.0 in the tested paths. Given there are already sufficient +1 votes and some areas still need further investigation, I wouldn’t want to block the release of these findings. Thanks Am Do., 26. März 2026 um 23:33 Uhr schrieb Bret McGuire < [email protected]>: > +1 > > Same validation steps used for the 2.0.0 release: > > > - Validated all signatures > - Validated the tag and commit > - Confirmed "go build" worked without issue > - Confirmed "go test" passed > - Ran a simple test app (accessing and printing release_version on > system.local) using the downloaded tarball as the gocql module > > > On Thu, Mar 26, 2026 at 1:02 PM James Hartig <[email protected]> > wrote: > >> +1 >> >> Updated several internal applications to v2.1.0-tentative and they ran >> without issues. >> >> On Thu, Mar 26, 2026, at 11:34 AM, Josh McKenzie wrote: >> >> +1 >> >> Checked keys and checksums >> >> On Wed, Mar 25, 2026, at 1:27 PM, João Reis wrote: >> >> Hey folks, >> >> I’m proposing the Apache Cassandra GoCQL Driver 2.1.0 for release. >> >> sha1: b86c662e14e223d2c85b68c05b537f52e25ed9d6 >> git: >> https://github.com/apache/cassandra-gocql-driver/tree/v2.1.0-tentative >> >> The Source release is available here (83391): >> >> https://dist.apache.org/repos/dist/dev/cassandra/cassandra-gocql-driver/2.1.0/ >> >> A major highlight of this release is a revamped internal schema metadata >> system. This overhaul has already allowed us to optimize the token-aware >> policy and introduce new configuration options for users to implement >> custom schema and node event listeners. >> >> This release also bumps the officially supported Go versions to 1.25 and >> 1.26. >> >> To avoid any premature access to this release before the vote is complete >> we’ve temporarily used the tag “v2.1.0-tentative” to clearly indicate that >> this tag points to a tentative release. Once the vote passes this tag will >> be updated to “v2.1.0”. >> >> The vote will be open for 72 hours (longer if needed). Everyone who has >> tested the build is invited to vote. Votes by PMC members are considered >> binding. A vote passes if there are at least three binding +1s and no -1s. >> >> If you are interested in contributing to the testing of this release here >> are some ways you can do so: >> >> - Download artifacts from the subversion repo linked above and verify >> signature (using KEYS[1]) and checksums >> - Build the source tarball and ensure tests pass (you can use the >> provided Makefile) >> - Upgrade gocql on an existing project or test app and run their >> testing suite >> >> >> Thanks, >> João >> >> [1] https://dist.apache.org/repos/dist/release/cassandra/KEYS >> >> >> >>
