# Last week in scylladb.git master (issue #248; 2024-09-22)

**URL:** <https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-248-2024-09-22/2940>\
**Category:** ScyllaDB\
**Tags:** git-news\
**Created:** [September 22, 2024, 1:46pm UTC](https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-248-2024-09-22/2940 "2024-09-22T13:46:43Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![avikivity](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/avikivity/32/38_2.png) [@avikivity](https://forum.scylladb.com/u/avikivity)\
**Post date:** [September 22, 2024, 1:46pm UTC](https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-248-2024-09-22/2940/1 "2024-09-22T13:46:43Z")

</div>

This short report brings to light some interesting commits to [scylladb.git master](https://github.com/scylladb/scylladb/) from the last week. Commits in the 6d8e9645ce…3d781c4fc8 range are covered.

There were 119 non-merge commits from 18 authors in that period. Some notable commits:

  

A CQL filtering bug when a regular column was filtered but no regular columns were selected was [fixed](https://github.com/scylladb/scylladb/commit/b9bc783418fe37f60bc3d3ccb34444aafdfaed97).

A recently-introduced memory leak in the Paxos implementation was [fixed](https://github.com/scylladb/scylladb/commit/695f112795af43769227dba095fa1ddae6e99207).

Compaction CLEANUP jobs now [run under the maintenance/streaming](https://github.com/scylladb/scylladb/commit/626f55a2ea2c3172c3cb33039392166a8f60fbf6) scheduling/group.

The version in the master branch was [updated to 6.3](https://github.com/scylladb/scylladb/commit/66c0814c3342e80f5c05376a0f02f139499b8c5c), indicating the beginning of the 6.2 stabilization cycle.

The test suite [now collects resource consumption metrics](https://github.com/scylladb/scylladb/commit/bbb6c3c2ff1779cd9a49cbca47f7cdb31b53f11d) and stores them in a local database. This will be used in the future to improve resource utilization.

The system will now [negotiate](https://github.com/scylladb/scylladb/commit/cc5c3aaae743976e388b3c40d04fb4b23e1545a5) the ability to run cross-node queries under the maintenance scheduling group.

The backup API now supports a [prefix parameter](https://github.com/scylladb/scylladb/commit/924325fd25bfc6b3c3b93bc28c82d75562c71a1d), allowing more fine-grained of where the backup is stored.

Some bugs were [fixed](https://github.com/scylladb/scylladb/commit/2f4f0eb060ef4e2fb20bcb8039184094ee77c536) in Alternator role-based access control.

The diagnostics dump from reader\_concurrency\_semaphore was [improved](https://github.com/scylladb/scylladb/commit/eb22c2a8c8c0899a718785f70be760de7e1e17d6).

Lightweight transaction query processing will move to the shard that owns the data, if it is not already there. It now recognizes that the owning shard could have moved again, due to tablet migration, and [retries](https://github.com/scylladb/scylladb/commit/6f7c2ce0aacbdde1dfd5a4ecda5432dd915e8816).

It is now possible to reroute an individual statement to a [different service level](https://github.com/scylladb/scylladb/commit/7e7701d436ed8926e94912772d77d1eb0c46b3f9); previously a different login session was required. This is useful for drivers to reduce the strain from the login queries.

  

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