Details
-
Improvement
-
Status: Triage Needed
-
Normal
-
Resolution: Unresolved
-
None
-
None
-
None
-
All
-
None
Description
This is an umbrella ticket to discuss removing pre-4.0 compatibility code from 5.0, similar to CASSANDRA-12716 for 4.x.
A few considerations:
- Discuss/ratify removal of pre-compatibility code on dev mailing list
- What compatibility features are being removed?
- What upgrade tests are being removed ? Are they still relevant and can be reused?
- Should upgrade from 3.x to 5.X fail on startup with an override flag?
- Can/should we make it easier to deprecate/remove compatibility code for future major releases?
Attachments
Issue Links
- relates to
-
CASSANDRA-18999 Gossiper::hasMajorVersion3Nodes returns true when a cluster is upgrading patch version without Cassandra 3 nodes.
- Resolved
-
CASSANDRA-12716 Remove pre-3.0 compatibility code for 4.0
- Resolved