Last week in scylladb.git master (issue #178; 2023-05-07)

This short report brings to light some interesting commits to scylladb.git master from the last week. Commits in the a93e5698b0…aba31ad06c range are covered.

There were 142 non-merge commits from 15 authors in that period. Some notable commits:

The check for altering permissions of functions in the system keyspace has been tightened.

Error messages involving the CQL token function have been improved.

In Alternator, ScyllaDB’s implementation of the DynamoDB API, validation of decimal numbers has been improved.

ScyllaDB sometimes caches a running query in order to resume it later. In order to do that, it must also store the position at which the query is at, since the cached query might get purged before it is resumed. To do that, it must scan over range tombstones to get to a non-ambiguous primary key position. A bug caused this scan to not terminate, resulting in the query running out of memory. This is now fixed.

A crash during shutdown due to incorrect service ordering was fixed.

The S3 object-storage driver can now sign multipart-upload requests, enabling it to work with Amazon S3, not just its clones.

The sstable validator had a bug in range tombstone validation fixed.

The reader_concurrency_semaphore managed memory and concurrency for read queries on replicas. Over time it has evolved, so various internal state names have grown out-of-sync with their actual meaning. The names have been adjusted to reflect their current meaning.

The documentation now reflects that ScyllaDB 5.2.0 has been released and is the stable branch.

See you in the next issue of last week in scylladb.git master!