Replace LeveledCompactionStrategy (LCS) with Cassandra 5.x default UnifiedCompactionStrategy (UCS) in schema.cql
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 87/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Quiet
- Domain
- databases, distributed-systems
Research direction
Read /cassandra/temporal/schema.cql and locate the table definitions containing WITH COMPACTION clauses. Remove those explicit clauses from each table, then verify that schema.cql no longer hardcodes LCS while preserving the existing table definitions and version-compatible defaults.
Written by the indexing model from the issue text.
Description
Description
The Cassandra schema file /cassandra/temporal/schema.cql currently configures nearly all tables with LeveledCompactionStrategy (LCS). LCS is not a good general-purpose default — it's optimized for read-heavy workloads with low write amplification tolerance, and imposes unnecessary compaction overhead for tables that don't need it.
Cassandra 5.0 introduces UnifiedCompactionStrategy (UCS) as the new default, which is designed to work well as a general-purpose strategy across a broader range of workloads.
Describe the solution you'd like
Remove the explicit WITH COMPACTION = {...} clause from each table definition in schema.cql. Dropping the clause lets each table fall back to the engine's default compaction strategy:
On Cassandra 5.x, this will default to UnifiedCompactionStrategy (UCS).
On earlier Cassandra versions, this will default to SizeTieredCompactionStrategy (STCS), so backward compatibility is preserved.
This avoids hardcoding a compaction strategy choice in the schema and lets each Cassandra version apply its own sensible default.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 200
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from temporalio/temporal
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
temporalio/temporal#12192 ·
-
potential-bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
temporalio/temporal#12126 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
temporalio/temporal#11989 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
temporalio/temporal#11780 · 3 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
temporalio/temporal#11534 · 2 comments ·
All issues in temporalio/temporal
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100