# Last week in scylladb.git master (issue #323; 2026-06-21)

**URL:** <https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-323-2026-06-21/5417>\
**Category:** ScyllaDB\
**Tags:** git-news\
**Created:** [June 21, 2026, 6:40pm UTC](https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-323-2026-06-21/5417 "2026-06-21T18:40:46Z")\
**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:** [June 21, 2026, 6:40pm UTC](https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-323-2026-06-21/5417/1 "2026-06-21T18:40:47Z")

</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 a74c9d7268d..5d1840c4db4 range are covered.

There were 112 non-merge commits from 29 authors in that period. Some notable commits:

  

The DELETE statement can [bypass](https://github.com/scylladb/scylladb/commit/c085eabb212a56c823bd9a9b7d524f34129c90b4) the large data guardrails so an administrator can delete large partitions. Note that with log-structured merge trees, deletions extend the partition until compaction is able to actually reduce data size.

The large data guardrails now [detect](https://github.com/scylladb/scylladb/commit/aa176c3173a49aef112f377c110d46489c2f74c5) oversized rows and collections in memtables too.

Atomic deletion of multiple sstables is needed to prevent data resurrection in case of a crash. It is now [implemented](https://github.com/scylladb/scylladb/commit/f412c3883848f8504b1f41b3b40aa1c7091550f3) for object-storage backed tables.

The build toolchain is now based on [Fedora 44](https://github.com/scylladb/scylladb/commit/e62fcc5e73be74141aa4d4fa887920c04f147e30), with clang 22 and libstdc++ 16.

There is now a metric for client timestamp drift compared to the server. This can [detect queuing](https://github.com/scylladb/scylladb/commit/0c398ecbf9059aac3f390178b849ea60688bd204) in TCP or in the server TCP stack itself.

Object storage client memory can now be [tuned](https://github.com/scylladb/scylladb/commit/ddd6465ce215214cc88704637daba8626c8b2c28) with a configuration item.

A node will [refuse](https://github.com/scylladb/scylladb/commit/9f9461076759fb7782803561cd4d79271250ed87) to decommission if it is the last node in a rack that is in use. Remove replication to a rack before removing its nodes.

A new CQL system function [BM25()](https://github.com/scylladb/scylladb/commit/37e60ac06b28f4b28374d638ce7beab9f7d54cab) allows computing the score for full-text searches as well as specifying the order.

The compaction manager keeps an estimate of the compaction backlog to allocate bandwidth for compaction, with higher backlog causing higher compaction bandwidth. It now [updates the estimate](https://github.com/scylladb/scylladb/commit/817c3fb0659dc5718a531de5acc55c22bc607aab) on memtable flush, not just compaction completion.

Strongly consistent tables (experimental) [improved handling](https://github.com/scylladb/scylladb/commit/08596ce2115c7e01fc095c6eff31d809f65ed8e0) of raft leaders believed to be down.

Tablet migrations for replication factor changes now take into account the [target disk size](https://github.com/scylladb/scylladb/commit/433135aa90e440e6285fb513ddd751506b51292c), like regular tablet migrations.

The large data guardrails can now return [CQL warnings](https://github.com/scylladb/scylladb/commit/7f5a7bb59aec8da90cadd75cc05b6da815349f34) from the coordinator to the client.

A bug in full scans while a vnodes-to-tablets migration is running [was fixed](https://github.com/scylladb/scylladb/commit/1726711a00fdf4539ed983363fde5518a452ca48).

Tablet-aware restore will now [set the tablet count](https://github.com/scylladb/scylladb/commit/2067ef11c4e213af31ed6c81052b29fe8ad46c5d) on the target table to avoid unnecessary tablet splits.

Connections to IP addresses that are no longer part of the cluster due to IP address changes are now [eagerly terminated](https://github.com/scylladb/scylladb/commit/a2bb0305ad46b5fcc8c61c7988e5cee1a3729bba) to avoid waiting for TCP timeouts. This improves recovery on Kubernetes.

  

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