# Last three weeks in scylladb.git master (issue #280; 2025-06-01) **URL:** \ **Category:** ScyllaDB\ **Tags:** git-news\ **Created:** [June 1, 2025, 9:00am UTC](https://forum.scylladb.com/t/last-three-weeks-in-scylladb-git-master-issue-280-2025-06-01/4870 "2025-06-01T09:00:52Z")\ **Posts on this page:** 1\ **Page:** 1
**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 1, 2025, 9:00am UTC](https://forum.scylladb.com/t/last-three-weeks-in-scylladb-git-master-issue-280-2025-06-01/4870/1 "2025-06-01T09:00:52Z")
This short report brings to light some interesting commits to [scylladb.git master](https://github.com/scylladb/scylladb/) from the last three weeks. Commits in the 092a88c9b9..7d562c24b1 range are covered. There were 198 non-merge commits from 31 authors in that period. Some notable commits: When loading sstables into the database with nodetool, there is now a [–skip-cleanup](https://github.com/scylladb/scylladb/commit/9f8de9adc8efcde55285b652ae25fb5cd26e0191) option when the user wishes to defer cleanup to a later time. This allows a single cleanup operation to be run for many sstable loads. Materialized view updates perform a read-modify-write operation on the base table. To prevent overload, we queue some of the reads. Previously, this queue had a limit of some number of entries beyond which reads would be rejected. This could cause base/view inconsistencies. The queue limit is now [removed](https://github.com/scylladb/scylladb/commit/59206476178423b63d98b5b9862bcd4743d481c6) and we rely on throttling the base table writes to control its length. Some alternator tests were [migrated](https://github.com/scylladb/scylladb/commit/c15cf54e3d01e9678933f631b61971d865927be0) from dtest to test.py. This marks the beginning of an effort to migrate all dtests into scylladb.git. We now manage [temporary memory for zstd](https://github.com/scylladb/scylladb/commit/185a032044c8555222bc91ccee61ba5dcb985ef5) inter-node compression ourselves, in order to reduce allocation stalls. The compaction history table now has [additional columns](https://github.com/scylladb/scylladb/commit/485df63fd50f70d8e6601e2836a7e008acbdedb6) for statistics. There is now a [custom index class](https://github.com/scylladb/scylladb/commit/61581d458ea0d4830c4994a2b5f3ba293d25e849) (useful in CREATE INDEX) for vector indexes. Note it is not yet possible to query using the new index. The native CQL transport now supports the [metadata ID extension](https://github.com/scylladb/scylladb/commit/c00824c7df74090ac4e862b4a728eaaec21ce5d4) (from protocol version 5) that allows updating row metadata for prepared statements for `SELECT *` queries (when columns were added or removed) or `SELECT udt` queries (when the user define type definition changed). Note a driver that supports the extension is required to make use of this. The `nodetool refresh` command now supports the [–scope](https://github.com/scylladb/scylladb/commit/c570941692fb4a9eacb1d60594a80649f7c90326) option, allowing data to be streamed only to the local node, local rack or local datacenter. This is useful when restoring from a backup that contains individual sstable sets for each rack. A bug which could cause data resurrection in materialized views (but not in the base tables) due to mixing up purge times for regular tombstones and shadowable tombstones was [fixed](https://github.com/scylladb/scylladb/commit/7db956965e6d9cc5a8915a8fe94e5f217738398f). The process for merging tablets (which happens when a table’s size decreases) did not update the row cache about the merged sstables, causing some data to be missed during full scans. This is now [fixed](https://github.com/scylladb/scylladb/commit/c52aec3d2fbbdb8b94bf454b58674a36d73f0df2). See you in the next issue of last week in scylladb.git master!