The ScyllaDB team announces ScyllaDB Open Source 5.0.7, a bugfix release of the ScyllaDB 5.0 stable branch. ScyllaDB Open Source 5.06, like all past and future 5.x.y releases, is backward compatible and supports rolling upgrades.
Note that the latest stable branch of ScyllaDB is 5.1, and you are encouraged to upgrade.
- ScyllaDB Open Source 5.0
- Get ScyllaDB Open Source - AWS AMI, GCP Docker, binary packages and unified installer
- ScyllaDB Web Installer for Linux (all releases)
- Upgrade from ScyllaDB Open Source 5.x.y to Scylla Open Source 5.x.z
- Upgrade from ScyllaDB Open Source 4.6.x to 5.0.y
- Please let us know if you encounter any problems.
Issues fixed in this release:
- CQL: Other restrictions ignored when clustering key is constrained #6200 #12014
- Alternator: wrong IS NOT NULL condition for GSI range key #11800
- Stability: segmentation fault in cases where the base table schema change while MV schema is cached #10026, #11542
- Stability: UndefinedBehavior in repair_reader::make_reader #10882
- Stability: The view builder is responsible for building materialized views when a view is created and after repair. To control its memory consumption, it reads base table sstables in chunks. Due to a bug, it could forget the partition tombstone or an open range tombstone when moving between chunks, leading to a discrepancy between the base table data and the view data. This is now fixed. #11668
- Stability: unpop partition header of spent partition in multishard mutation query. With the fix, Scylla does not resume an already exhausted partition at the start of generating a new page. #9482
- Stability: LWT insert crash if clustering key is null #11954