The patch will need vetting for compatibility implications of upgrades from (e.g.,)
4.0 + CEP-37 to newer-versioned releases like Apache Cassandra 5.0.6 that don't have
this change. Some sources of potential incompatibility (briefly scanned, not vetted)
look like: – Table params:
https://github.com/apache/cassandra/commit/6753fb49dcba6af6cccc02e62a5d425704d45b20#diff-44546e8ca2f2a8a986ec2b16f837b7526f2444e5fb2c6367abf35d8756fd0e51R578-R631
– system_distributed generation bump:
https://github.com/apache/cassandra/commit/6753fb49dcba6af6cccc02e62a5d425704d45b20#diff-68edc51628c3cf6a0e9dbcff0dd697e130b952e0f328699db5541a21300aa0b2R89-R104
– System table:
https://github.com/apache/cassandra/commit/6753fb49dcba6af6cccc02e62a5d425704d45b20#diff-68edc51628c3cf6a0e9dbcff0dd697e130b952e0f328699db5541a21300aa0b2R166
On Dec 2, 2025, at 11:36 AM, Josh McKenzie <[email protected]> wrote: In a
couple prior discuss threads, the topic of backporting in-project repair scheduling
(CEP-37) came up a few times and the consensus seemed to be that everyone was
receptive to us backporting this feature to all GA branches. The goal of this thread
is to focus on that and formalize discussion and consensus before a potential vote.
Here's a link to the CEP-37:
https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-37%3A+Apache+Cassandra+Unified+Repair+Solution
And a link to the JIRA for the impl:
https://issues.apache.org/jira/browse/CASSANDRA-19918 And here's the PR:
https://github.com/apache/cassandra/commit/6753fb49dcba6af6cccc02e62a5d425704d45b20
So: what do we think? I'm personally +1 on allowing this to be backported to 4.0,
4.1, and 5.0. ----- Prior reading: - Discussing potential of a backport branch:
https://lists.apache.org/thread/xbxt21rttsqvhmh8ds9vs2cr7fx27w3k - Discussing
understanding fork motivations:
https://lists.apache.org/thread/5nv1f4bng4nw5ofgh135k5pf2f6l6lgl
