v1.7.0

Changed

• Update DRIVER_NAME parameter in STARTUP messages to a different value intended to clearly identify this driver as an ASF driver. This should clearly distinguish this release (and future gocql-cassandra-driver releases) from prior versions. (#1824)
• Supported Go versions updated to 1.23 and 1.22 to conform to gocql's sunset model. (#1825)

v1.6.0

Added

• Added the InstaclustrPasswordAuthenticator to the list of default approved authenticators. (#1711)
• Added the com.scylladb.auth.SaslauthdAuthenticator and com.scylladb.auth.TransitionalAuthenticator
  to the list of default approved authenticators. (#1712)
• Added transferring Keyspace and Table names to the Query from the prepared response and updating
  information about that every time this information is received. (#1714)

Changed

• Tracer created with NewTraceWriter now includes the thread information from trace events in the output. (#1716)
• Increased default timeouts so that they are higher than Cassandra default timeouts.
  This should help prevent issues where a default configuration overloads a server using default timeouts
  during retries. (#1701, #1719)

v1.5.2

Same as v1.5.0 (GitHub was not able to verify signature with embedded cleartext gpg message, even with armor lines prefixed)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

2023-06-12:
Switching signing key used for github.com/gocql/gocql tags (since v1.5.0)
from GPG key ID: E0C5EC9218CB255D
to SSH key with the following fingerprint:
SHA256:TcKxeY58a0HRfycY4dCuqMF23FrNyEcclOdVzUI9BBI
You can verify it with
[email protected] namespaces="git" ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIN8Cnim2/FWQqDJmhidmXK/9VNO64rLfVJrvZqKaLqUl
in your gpg.ssh.allowedSignersFile
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEW7CgRMsA2lq5yf6v4MXskhjLJV0FAmSHOcYACgkQ4MXskhjL
JV2IXhAAye6kQhLwiiCag6bHUKIbKxM0TQHiOZf7aRKYlU2s0aWcsOXMeS6S9pvC
cJqmjBdhDZx569bPrgjAy9+jMoe+rNBR5Cr8dcJUk31cKUTjm/7PsKfiCxfDrbnm
ARDY2Z3vdGJC39mvBjG16UurzAPlRnP66jzyWYaXBiFBJJGWkP1+m+PNG4eF9ggo
6W89MEeK6ZpLCxI0URq2RyB5JEgGkr1Gb9UB4/70euiTjUxeRjS+RHjosGREC0nG
MxfpHND/Z+gOhHXCYt87zrF7N7JWIFU3+4vOj/th8MvMGRYaDzOAKT7MQmc/wc3A
drBA5G/adltjNw9aWTRQGNV69jhaoaIkZfv4fy+AvPDz41iGOQD9Nulw8ujkocUC
8zr4OxPhc0LIX1LtqwA2ahYfJABXnC7ObzqZLyXsE0sW5yvWpPNlF+Bj/slAdO+6
d+4uxGs8dd3N/bOihFL2XZoeOStF6ehT5KIFsbr885FUueu6iRgZYPalfv/aWe95
VIh97ikNsfgFH3mO0ZTGP9tnjSCbGIwG2Oh3+0dj5J4tZU1ihJRKiHJJNQirG1xK
jMdu9EXOEPFK4CPwaXZgHpTy38cFF2MOxHbsrxErCuWJY8JxRpqlJeOyx0F+eTR4
NGQSrMKvxfKd/F192UznSUSfflRTrQT7stUOhZk3Lc4YcCSiDEk=
=em6i
-----END PGP SIGNATURE-----

v1.5.1

Same as v1.5.0 (GitHub was not able to verify signature with embedded cleartext gpg message)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

2023-06-12:
Switching signing key used for github.com/gocql/gocql tags (since v1.5.0)
from GPG key ID: E0C5EC9218CB255D
to SSH key with the following fingerprint:
SHA256:TcKxeY58a0HRfycY4dCuqMF23FrNyEcclOdVzUI9BBI
You can verify it with
[email protected] namespaces="git" ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIN8Cnim2/FWQqDJmhidmXK/9VNO64rLfVJrvZqKaLqUl
in your gpg.ssh.allowedSignersFile
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEW7CgRMsA2lq5yf6v4MXskhjLJV0FAmSHOcYACgkQ4MXskhjL
JV2IXhAAye6kQhLwiiCag6bHUKIbKxM0TQHiOZf7aRKYlU2s0aWcsOXMeS6S9pvC
cJqmjBdhDZx569bPrgjAy9+jMoe+rNBR5Cr8dcJUk31cKUTjm/7PsKfiCxfDrbnm
ARDY2Z3vdGJC39mvBjG16UurzAPlRnP66jzyWYaXBiFBJJGWkP1+m+PNG4eF9ggo
6W89MEeK6ZpLCxI0URq2RyB5JEgGkr1Gb9UB4/70euiTjUxeRjS+RHjosGREC0nG
MxfpHND/Z+gOhHXCYt87zrF7N7JWIFU3+4vOj/th8MvMGRYaDzOAKT7MQmc/wc3A
drBA5G/adltjNw9aWTRQGNV69jhaoaIkZfv4fy+AvPDz41iGOQD9Nulw8ujkocUC
8zr4OxPhc0LIX1LtqwA2ahYfJABXnC7ObzqZLyXsE0sW5yvWpPNlF+Bj/slAdO+6
d+4uxGs8dd3N/bOihFL2XZoeOStF6ehT5KIFsbr885FUueu6iRgZYPalfv/aWe95
VIh97ikNsfgFH3mO0ZTGP9tnjSCbGIwG2Oh3+0dj5J4tZU1ihJRKiHJJNQirG1xK
jMdu9EXOEPFK4CPwaXZgHpTy38cFF2MOxHbsrxErCuWJY8JxRpqlJeOyx0F+eTR4
NGQSrMKvxfKd/F192UznSUSfflRTrQT7stUOhZk3Lc4YcCSiDEk=
=em6i
-----END PGP SIGNATURE-----

v1.5.0

Added

• gocql now advertises the driver name and version in the STARTUP message to the server.
  The values are taken from the Go module's path and version
  (or from the replacement module, if used). (#1702)
  That allows the server to track which fork of the driver is being used.
• Query.Values() to retrieve the values bound to the Query.
  This makes writing wrappers around Query easier. (#1700)

Fixed

• Potential panic on deserialization (#1695)
• Unmarshalling of dates outside of [1677-09-22, 2262-04-11] range. (#1692)

v1.4.0

Changed

• gocql now refreshes the entire ring when it receives a topology change event and
  when control connection is re-connected.
  This simplifies code managing ring state. (#1680)
• Supported versions of Cassandra that we test against are now 4.0.x and 4.1.x. (#1685)
• Default HostDialer now uses already-resolved connect address instead of hostname when establishing TCP connections (#1683).

Fixed

• Deadlock in Session.Close(). (#1688)
• Race between Query.Release() and speculative executions (#1684)
• Missed ring update during control connection reconnection (#1680)

v1.3.2

Changed

• Supported versions of Go that we test against are now Go 1.19 and Go 1.20.

Fixed

• Node event handling now processes topology events before status events.
  This fixes some cases where new nodes were missed. (#1682)
• Learning a new IP address for an existing node (identified by host ID) now triggers replacement of that host.
  This fixes some Kubernetes reconnection failures. (#1682)
• Refresh ring when processing a node UP event for an unknown host.
  This fixes some cases where new nodes were missed. (#1669)

v1.3.1

Fixed

• Panic in RackAwareRoundRobinPolicy caused by wrong alignment on 32-bit platforms. (#1666)

v1.3.0

Added

• Added a RackAwareRoundRobinPolicy that attempts to keep client->server traffic in the same rack when possible.

Changed

• Supported versions of Go that we test against are now Go 1.18 and Go 1.19.

v1.2.1

Changed

• GetCustomPayload now returns nil instead of panicking in case of query error. (#1385)

Fixed

• Nil pointer dereference in events.go when handling node removal. (#1652)
• Reading peers from DataStax Enterprise clusters. This was a regression in 1.2.0. (#1646)
• Unmarshaling maps did not pre-allocate the map. (#1642)