[CASSANDRA-18441] Improvements to SSTable format configuration

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 5.0-alpha1, 5.0
• Component/s: Local/SSTable
• Change Category: Semantic
• Complexity: Normal
• Platform: All

Source Control Link

https://github.com/apache/cassandra/commit/fe0e04c2319afab958b3da83e7b54c84bced9dc2

Test and Documentation Plan

regression tests

• Assignee: Jacek Lewandowski Assign to me
• Reporter: Branimir Lambov

Authors

Jacek Lewandowski

Reviewers

David Capwell

• Created: 11/Apr/23 11:20
• Updated: 12/Sep/23 13:02
• Resolved: 18/May/23 10:58

Description

CEP-17 and CASSANDRA-17056 abstracted some interfaces for SSTable format implementations and defined a method of plugging in specific configurations.

This method is brittle and asks users to specify format identifiers whose configuration does not provide value but can be the source of conflicts and problems. On the other hand it makes important choices non-obvious, as the selection of format to write is given by the order of configured interfaces.

An improved specification mechanism needs to be put in place before Cassandra 5 is released.

Issue Links

• is depended upon by: CASSANDRA-18533 Move format-specific sstable options into the format configuration
• is depended upon by: CASSANDRA-18534 Make sstable format configurable per table
• is related to: CASSANDRA-17056 CEP-17 – Pluggable SSTable format (SSTable format API)
• is related to: CASSANDRA-18398 CEP-25: Trie-indexed SSTable format