# Last week in scylladb.git master (issue #167; 2023-02-12)

**URL:** <https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-167-2023-02-12/319>\
**Category:** ScyllaDB\
**Tags:** git-news\
**Created:** [February 12, 2023, 11:32am UTC](https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-167-2023-02-12/319 "2023-02-12T11:32:45Z")\
**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:** [February 12, 2023, 11:32am UTC](https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-167-2023-02-12/319/1 "2023-02-12T11:32:45Z")

</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 61dfc9c10f…ca4db9bb72 range are covered.

There were 129 non-merge commits from 18 authors in that period. Some notable commits:

  

The row cache and memtables now hold rows and range tombstones in a unified data structure, rather than in separate data structures. This [solves](https://github.com/scylladb/scylladb/commit/f73e2c992f77b829037833c4f46a9237cb92d76a) performance problems (throughput and latency) when a large partition had many range tombstones.

A recently-introduced bug, where a prepared statement with named bind variables was executed without providing a value for one of the variables was [fixed](https://github.com/scylladb/scylladb/commit/2a5ed115caa072c11ccd2d275c6a800d6cdd3073).

Repair-based node operations was made the [default](https://github.com/scylladb/scylladb/commit/1e6cc9ca6132ad92796f86e267640d869a23dae0). However, after problems surfaced in continuous integration, it was [reverted](https://github.com/scylladb/scylladb/commit/fd4ee4878ab6814c5cc119c7538ac0eafa560afb) again.

The port option in SSTableLoader was [fixed](https://github.com/scylladb/scylladb/commit/5a9f75aac6aa1f48516d9c7721fb0afcc36ca3d4).

The check for whether a user defined function is in use by a user defined aggregate before dropping it has been [improved](https://github.com/scylladb/scylladb/commit/cc207a9f4488961780afff9ea844726c6f27630c).

A crash duing cql3 aggregation, for the case the query returned no results, has been [fixed](https://github.com/scylladb/scylladb/commit/3ba011c2bef8c265f7f6b53869b36ef1739c62b8).

ScyllaDB will now treat [running out of disk quota](https://github.com/scylladb/scylladb/commit/051da4e148234cf4b9ee9080ae5477919c4c0ca8) (EDQUOT) in the same way it treats running out of disk space (ENOSPC).

An edge case where a vnode token boundary coincided with a range scan boundary, but inclusiveness/exclusiveness of the token (`<` vs `<=`) did not agree, has been [fixed](https://github.com/scylladb/scylladb/commit/95bf8eebe003d692e4fdd8c751dda06e5af08ed2).

Some minor bugs in the cql transport server error handling have been [corrected](https://github.com/scylladb/scylladb/commit/1c333e2102d4a9e6e7be589cb5829e7f2171a5f4).

Repair will now [ignore](https://github.com/scylladb/scylladb/commit/e2064f4762d0ac64104c76cbdbb20ce0c90d77da) local keyspaces.

  

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