# Last week in scylladb.git master (issue #156; 2022-11-27)

**URL:** <https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-156-2022-11-27/113>\
**Category:** Database Community\
**Tags:** git-news\
**Created:** [November 27, 2022, 9:59am UTC](https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-156-2022-11-27/113 "2022-11-27T09:59:13Z")\
**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:** [November 27, 2022, 9:59am UTC](https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-156-2022-11-27/113/1 "2022-11-27T09:59:13Z")

</div>

This short report brings to light some interesting commits to scylladb.git master from the last week. Commits in the 41629e97de…996eac9569 range are covered.

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

A regression where CQL ignored some WHERE clause components when a multi-column restriction ((col\_a, col\_b) \< (0, 0)) was present was [fixed](https://github.com/scylladb/scylladb/commit/2d2034ea28b8615a130146ad9780010d29d2fcc9).

The bundled cqlsh now uses the [ScyllaDB Python driver](https://github.com/scylladb/scylladb/commit/14218d82d60b7881af2fcb328dc4485837cc5514) (rather than the generic Cassandra driver) and supports Scylla Cloud connection bundles.

When a query completes a page, ScyllaDB caches the query activity as an inactive read. When the client requests the next page, ScyllaDB re-activates the read and continues where it left off. A bug in this mechanism that could cause crashes has been [fixed](https://github.com/scylladb/scylladb/commit/15ee8cfc05c73e87e66b588ac1be090b3f9105f8).

There is now [documentation](https://github.com/scylladb/scylladb/commit/40f61db1205dbf57645a0e2b349ea1011f14d669) for the (mostly automatic) procedure to upgrade a cluster to use Raft, and for the manual procedure to recover in case of problems.

A bug in alternator WHERE condition for global secondary index range key, that does not appear to have any user visible impact, has been [fixed](https://github.com/scylladb/scylladb/commit/ce7c1a6c52dd4b136088e7b69da45aa4becd7ec1).

The task manager is now [aware](https://github.com/scylladb/scylladb/commit/602dfdaf9818320fe2de01e3270a8245d30302ac) of repair-related tasks.

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