# Last week in scylladb.git master (issue #285; 2025-07-14)

**URL:** https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-285-2025-07-14/4981
**Category:** ScyllaDB
**Created:** [July 14, 2025, 6:23pm UTC](https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-285-2025-07-14/4981 "2025-07-14T18:23:40Z")
**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: [July 14, 2025, 6:23pm UTC](https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-285-2025-07-14/4981/1 "2025-07-14T18:23:40Z")

</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 33225b730d5..fdcaa9a7e79 range are covered.

There were 76 non-merge commits from 12 authors in that period. Some notable commits:

  

Tablet metadata can grow very large in large clusters. Its creation already avoided reactor stalls, and now its [destruction](https://github.com/scylladb/scylladb/commit/d4efefbd9cfd46e4a5a54e2daa42d193bddac038) as well.

The repair small table optimization is used to speed up repairs on tables that are empty or almost empty (like many tables in system\_distributed). On large clusters, the optimization could lead to an out-of-memory condition. This is now [fixed](https://github.com/scylladb/scylladb/commit/17272c2f3b1cf43df7167e9ebbb20a800e28b29e).

The vector search system [implements the client](https://github.com/scylladb/scylladb/commit/d9aec89c4ee70282ea4e980a5e998c2dd032bd4b) that accesses the external index.

Some stalls when managing schemas with thousands of tables were [eliminated](https://github.com/scylladb/scylladb/commit/3feb759943b7ba8fe1c80295d7e67457506374f1).

A new [schema application framework](https://github.com/scylladb/scylladb/commit/6fce817aa8bf948e959056aaf344a0f51228ea18) was merged, which will allow to improve atomicity when managing cluster metadata.

  

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