[
https://issues.apache.org/jira/browse/CASSANDRA-19243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17801027#comment-17801027
]
Paulo Motta commented on CASSANDRA-19243:
-----------------------------------------
It was identified on CASSANDRA-18999 that {{Gossiper::hasMajorVersion3Nodes
}}was removed from trunk, effectively removing pre-4.0 compatibility from trunk.
This [PR|https://github.com/apache/cassandra/pull/3004] removes the method
{{Gossiper::hasMajorVersion3Nodes}} from cassandra-5.0 branch, which removes
pre-4.0 compatibility from 5.0.
In addition to reviewing the changes above, we need to ensure that no more
pre-4.0 compatibility code remains in 5.0+
Since the backward compatibility code will be removed, I propose adding a new
StartupCheck to prevent upgrade from version < 4.0 and a flag to override (if
this is not already there).
> Remove pre-4.0 compatibility code for 5.0
> -----------------------------------------
>
> Key: CASSANDRA-19243
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19243
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Paulo Motta
> Priority: Normal
>
> 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?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
