[CASSANDRA-18314] Lift MessagingService.minimum_version to 40

• Type: Task
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 5.0-alpha1, 5.0
• Component/s: Messaging/Internode
• Epic Link: cassandra-post-4x-cleanup
• Change Category: Operability
• Complexity: Normal
• Platform: All

Source Control Link

https://github.com/apache/cassandra/commit/4bbfd64fcd7ff208c8cc3833ffff00aea015d2a8

Test and Documentation Plan

ci

• Assignee: Michael Semb Wever Assign to me
• Reporter: Michael Semb Wever

Authors

Michael Semb Wever

Reviewers

Andres de la Peña, Maxim Muzafarov

• Created: 09/Mar/23 13:16
• Updated: 07/Nov/23 12:11
• Resolved: 06/Nov/23 14:47

Description

MessagingService's VERSION_30 and VERSION_3014 don't have to be supported in Cassandra 5.0 anymore.

(Cassandra 5.0 currently is still using VERSION_40)

Patch: https://github.com/apache/cassandra/compare/trunk...thelastpickle:cassandra:mck/18314/trunk

Raises the question whether backward compatibility to the previous major is defined by the Cassandra version or by the internal component version (MessagingService).

Issue Links

• relates to: CASSANDRA-19002 Create / update tests to ensure commit logs and hints for all versions in MS are ingestible in 5.0
• Testing discovered: CASSANDRA-18703 Test failure: SSTablesSystemViewTest#testVirtualTableThroughIndexLifeCycle
• Testing discovered: CASSANDRA-18695 Remove 3.x from the versions checked for prepared statement behaviour
• links to: GitHub Pull Request #2506