[RELEASE] ScyllaDB 2026.1.7

Release Notes
, ,
1

The ScyllaDB team is pleased to announce the release of ScyllaDB 2026.1.7, a production-ready patch release for ScyllaDB 2026.1 Long Term Support (LTS) Release.

More information on ScyllaDB Version Support Policy is available here.

Related Links

Bug Fixes

The following issues are fixed in this release.

Storage

  • Trie-based SSTable indexes use a byte-comparable encoding of keys. The encoding used by SSTable format ms isn’t fully compatible with the canonical partition key ordering used elsewhere in the database. If the dataset contains two keys on which the two comparators give a different ordering, attempts to write them into an ms SSTable will fail with an exception, blocking compactions or flushes on the affected shard until the SSTable format is manually switched to an older version. SSTable format version ms is superseded by the new mt format, which uses a corrected encoding. After upgrading, ms SSTables will no longer be written. If sstable_format: ms is configured, it will behave as though sstable_format: mt were configured instead.
    scylladb#30406

Vector Search

  • Approximate Nearest Neighbor (ANN) queries that include restrictions on non-prefix primary key columns or partial partition key columns could trigger an out-of-bounds memory access, resulting in a node crash. Post-filtering in ANN queries now correctly delegates all filtering to the Vector Store component, preventing the node from attempting to access columns that were not retrieved.
    scylladb#30492