# Last week in scylladb.git master (issue #312; 2026-03-08)

**URL:** <https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-312-2026-03-08/5304>\
**Category:** ScyllaDB\
**Tags:** git-news\
**Created:** [March 8, 2026, 8:02pm UTC](https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-312-2026-03-08/5304 "2026-03-08T20:02:47Z")\
**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:** [March 8, 2026, 8:02pm UTC](https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-312-2026-03-08/5304/1 "2026-03-08T20:02: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 fb6eebc3831..fda68811e8a range are covered.

There were 137 non-merge commits from 30 authors in that period. Some notable commits:

  

The migration code from `system.batchlog` to `system.batchlog_v2` was [improved](https://github.com/scylladb/scylladb/commit/a83ee6cf669b822331b724b317eb8fadef006408). These tables are used to support `LOGGED BATCH` statements.

The `scylla sstable query` tool, used for offline query from sstables, now supports [nested user defined types](https://github.com/scylladb/scylladb/commit/6bf706ef1b28c3e72ce4b6ff461278687a3684cb).

The `scylla sstable` tool [learned](https://github.com/scylladb/scylladb/commit/ab532882dbd8f2451e0412f883006646f6e9a9f8) a `split` subcommand, used to split sstables offline.

One can now [set](https://github.com/scylladb/scylladb/commit/ab532882dbd8f2451e0412f883006646f6e9a9f8) a maximum tablet count on a table. This ensures fast restore by not requiring sstables to be split during restore.

Experimental strongly consistent tables use Raft to replicate data. They can now [store data on all shards](https://github.com/scylladb/scylladb/commit/85bd6d011493ad9ea7b5a112fc11072e730a9c9a), rather than just on shard 0, and employ all the compute power of the node.

The default superuser `cassandra` is [no longer created](https://github.com/scylladb/scylladb/commit/c7d3f8086356b5003bd42937f37ad1e01c2679cc), as the default password is well known. Instead, users can create a superuser via the maintenance socket.

The vector similarity functions (e.g. similarity\_cosine()) have improved performance via [compiler autovectorization](https://github.com/scylladb/scylladb/commit/212bd6ae1a6726866f6a5a0d5c50024f7db16a63).

There are now [guardrails](https://github.com/scylladb/scylladb/commit/c3f59e4fa18184f1a016210b31b86198e6cd9363) for write consistency level, used to prevent low durability writes.

The amount of memory reserved for TCP buffering was [reduced](https://github.com/scylladb/scylladb/commit/5ae40caa6d6e962b1ea42a4d0c322396b511eb3d) from 9% to 3%, to reduce the probability of a kernel out-of-memory event.

Tombstone garbage collection on RF=1 tables with tombstone\_gc=repair was [made to work](https://github.com/scylladb/scylladb/commit/7564a56dc834ade99e5ec12c8ba6a8305d228153).

A race condition between repair and tablet merge was [fixed](https://github.com/scylladb/scylladb/commit/509f2af8db80a3553e06d6e3020450e3bc57be36).

Incorrect sorting when both ORDER BY and functions were used as selectors was [fixed](https://github.com/scylladb/scylladb/commit/f9d213547fbaf8453d51d75f9d599437dd11ca79).

  

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