# Last week in scylladb.git master (issue #198; 2023-09-24) **URL:** \ **Category:** ScyllaDB\ **Tags:** git-news\ **Created:** [September 24, 2023, 12:07pm UTC](https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-198-2023-09-24/868 "2023-09-24T12:07:44Z")\ **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:** [September 24, 2023, 12:07pm UTC](https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-198-2023-09-24/868/1 "2023-09-24T12:07:44Z")
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 4eb4ac4634…99d83808cc range are covered. There were 124 non-merge commits from 16 authors in that period. Some notable commits: A security vulnerability that allowed table permissions to be taken over by an unauthorized user has been [fixed](https://github.com/scylladb/scylladb/commit/ab6988c52f889f81f7afc6656f7f2ec679c0c205). Without Raft-managed consistent schema, each node evolves its own schema and the cluster attempts to merge each node’s schema to produce a consistent outcome. To see if a consistent outcome was achieved, each node calculates a hash of its schema and then these hashes are compared. This is a fragile computation and sometimes leads to schema disagreement even though there is no real difference between nodes. This was carried over to raft-managed consistent schema, but now when Raft is enabled the [leader will decree a schema version](https://github.com/scylladb/scylladb/commit/3d4398d1b2b9bc2139718e49a806214171ee081f) and other nodes will learn it from the leader. This should eliminate schema disagreement problems when Raft consistent schema is enabled. Change Data Capture (CDC) funnels change information to a number of streams, which are dependent on current topology. As topology changes the streams change, and their identity is maintained in the CDC generations table. The table is now [garbage-collected](https://github.com/scylladb/scylladb/commit/bc6f7d1b20be6a50cc1baf3c8aa54902d1dbe0e0) to remove old streams. A reactor stall when creating CDC streams for large clusters has been [fixed](https://github.com/scylladb/scylladb/commit/62a8a31be7b0e22df36eaa7b6814e1cd6207327d). On startup, partially created sstables stored on object storage (e.g. S3) are now [removed](https://github.com/scylladb/scylladb/commit/f6575344df66820b042d8217a46e0b7eb809067b). The S3 driver can now use [temporary credentials](https://github.com/scylladb/scylladb/commit/c364efb998a48830b572472daaa729f709ba40e1). The S3 driver now [tracks its memory usage](https://github.com/scylladb/scylladb/commit/1da6a939fea73661ccb4bfdd6d03d7a8de17bb81) to avoid running out of memory. We now [abort running repairs](https://github.com/scylladb/scylladb/commit/6e972f85052e500615ad2d839ae01a08909813ee) on `nodetool drain` commands. In consistent topology mode, the leader now [prevents](https://github.com/scylladb/scylladb/commit/c94a9cf73158b3277741915752ccb56b45fd9cc3) the previous leader from affecting the cluster before starting its own changes. Off-strategy compaction is used to reshape sstables that weren’t created from memtable flushes or regular compaction, for example repair or bootstrap. It now uses [incremental compaction](https://github.com/scylladb/scylladb/commit/61440d20c3295accc72b44a68bbe20a260c8e0bf) for run-based compaction strategies (Leveled or Incremental compaction strategies), reducing temporary storage requirements. A bug in the fromJson() CQL function when operating on NULL operands has been [fixed](https://github.com/scylladb/scylladb/commit/a684e51e4de80d4615f1db8f50cc7271137d399a). Compaction strategy options are now validated [earlier](https://github.com/scylladb/scylladb/commit/91a8100b3f51acd76277c123369b422e98b232d8). See you in the next issue of last week in scylladb.git master!