Skip to content
This repository has been archived by the owner on Jan 2, 2023. It is now read-only.

Releases: iconara/cql-rb

v1.2.2

17 May 09:57
Compare
Choose a tag to compare

Bugfix release.

  • Fixes #100 where MAP<TEXT,X> where X is anything but TEXT could result in an encoding error.

v2.0.0.pre2

06 May 10:11
Compare
Choose a tag to compare
v2.0.0.pre2 Pre-release
Pre-release

Some improvements around UUIDs and batches, and a bugfix:

  • Performance and correctness improvements in the creation and encoding of UUIDs
  • Batches are now reusable
  • Fixed #99 (nothing was logged when a connection unexpectedly closed)

This is a stable release, but the API for v2.0 hasn't been frozen yet. There will most likely be very few changes between this release and v2.0.

v2.0.0.pre1

15 Mar 14:33
Compare
Choose a tag to compare

This is the first release of cql-rb that has an external dependency. The reason is that the IO, byte buffer and futures code has been moved to a separate library, Ione. I've used cql-rb to make other network clients and it started to get weird to have a Cassandra driver as a dependency for things that didn't talk to Cassandra.

There has also been a few fixes and additions:

  • Fixed a bug in Uuid#hash when running in JRuby (#81)
  • Added Uuid#to_i as an alias for #value (#82)
  • Made TimeUuid comparable (#83)

v1.2.1

07 Mar 07:26
Compare
Choose a tag to compare

Tiny bugfix release with a fix for #81.

v2.0.0.pre0

13 Feb 07:40
Compare
Choose a tag to compare
v2.0.0.pre0 Pre-release
Pre-release

This is the first prerelease towards 2.0 with full support for Cassandra 2.0 and v2 of the CQL binary protocol.

New features include:

  • Full support for Cassandra 2.0
  • Batches of mixed statements
  • Result paging
  • Bound variables in non-prepared statements
  • Prepared statements cache the result metadata for lower response overhead
  • SASL authentication support with pluggable authenticators

Please test and report any issues you find. This prerelease is feature complete and thouroughly tested in ideal conditions and limited inputs, but it needs to be proven in the real world to mature to a full v2.0.0.

v2.0 is fully backwards compatible with v1.2 and works with both Cassandra 2.0 and 1.2 (the version number correlation is mostly incidental, but I decided to go for 2.0 for this release because it looked good, it probably violates semver in some way).

v1.2.0

29 Jan 06:39
Compare
Choose a tag to compare

This release makes cql-rb feature complete with respect to v1 of the CQL binary protocol. It adds the following new features:

  • Support for request tracing
  • Support for frame compression (and a Snappy compression implementation is included)

In addition there's been some refactorings and optimizations in the frame encoding and decoding, and bug fixes in the reconnection logic (see release v1.1.3), as well as changes to the logging output.

v1.2.0.pre2

14 Jan 16:57
Compare
Choose a tag to compare
v1.2.0.pre2 Pre-release
Pre-release

Fixes a bug in the frame decoding introduced in v1.2.0.pre0

v1.2.0.pre1

14 Jan 14:45
Compare
Choose a tag to compare
v1.2.0.pre1 Pre-release
Pre-release

Only changes the logging that prepared statements do when they are prepared on a new node. They now print their ID and the node's ID and address.

v1.2.0.pre0

04 Jan 10:50
Compare
Choose a tag to compare
v1.2.0.pre0 Pre-release
Pre-release

v1.2 will make cql-rb feature complete with respect to v1 of the CQL binary protocol. It adds the following new features:

  • Support for request tracing
  • Support for frame compression (and a Snappy compression implementation is included)

In addition there's been some refactorings and optimizations in the frame encoding and decoding, and bug fixes in the reconnection logic (see release v1.1.3).

v1.1.3

04 Jan 10:48
Compare
Choose a tag to compare

Reconnection logic bugfixes for v1.1.x:

  • Fixes #63, the driver should no longer get stuck in endless reconnection attempts, and it will not attempt multiple parallel reconnections.
  • When new nodes were added the driver didn't discover them because it expected topology change events to have the value "UP", but in fact the correct value is "NEW_NODE".