[CASSANDRA-18673] Reduce size of per-SSTable index components

• Type: Improvement
• Status: Resolved
• Priority: Urgent
• Resolution: Fixed
• Fix Version/s: 5.0-alpha1, 5.0, 5.1
• Component/s: Feature/SAI
• Epic Link: Storage Attached Indexes (Phase 2)
• Change Category: Performance
• Complexity: Challenging
• Platform: All

Source Control Link

https://github.com/apache/cassandra/commit/655a2455ac29395b0a303e6ad7fc4d458b18932d

Test and Documentation Plan

Latest CI run here: https://app.circleci.com/pipelines/github/mike-tr-adamson/cassandra/230/workflows/e6312515-451b-491e-aafd-2ed08e0e2fd6

• Assignee: Mike Adamson
• Reporter: Mike Adamson

Authors

Mike Adamson

Reviewers

Andres de la Peña, Caleb Rackliffe

• Created: 17/Jul/23 15:29
• Updated: 15/May/24 20:32
• Resolved: 18/Aug/23 20:02

Description

The current per-SSTable index components are large because the primary keys that are stored in them include the token as part of the byte comparable. The byte comparable puts the token first meaning that we get very little prefix compression from either the trie or the sorted terms store.

We can fix this by removing the token from the primary key serialization. This would allow us to get the prefix compression from the trie and the sorted terms store.

Issue Links

• links to: GitHub Pull Request #2498