[CASSANDRA-14973] Bring protocol v5 out of beta, introduce v6 before 4.0 release is cut

• Type: Task
• Status: Resolved
• Priority: Urgent
• Resolution: Fixed
• Fix Version/s: 4.0-rc1, 4.0
• Labels: protocolv5
• Complexity: Normal
• Impacts: Clients

Source Control Link

https://github.com/apache/cassandra/commit/c9d6c725dd0b4aa5693eb1c6d2221c28e9e99c6e

Test and Documentation Plan

dtests updated to exercise new non-beta version

• Assignee: Sam Tunnicliffe
• Reporter: Alex Petrov

Authors

Sam Tunnicliffe

Reviewers

Alex Petrov, Eduard Tudenhoefner

• Created: 10/Jan/19 12:41
• Updated: 23/Apr/23 20:33
• Resolved: 23/Feb/21 16:56

Description

In http://issues.apache.org/jira/browse/CASSANDRA-12142, we’ve introduced Beta flag for v5 protocol. However, up till now, v5 is in beta both in Cassandra and in java-driver.

Before the final 4.0 release is cut, we need to bring v5 out of beta and finalise native protocol spec, and start bringing all new changes to v6 protocol, which will be in beta.

Issue Links

• causes: CASSANDRA-16508 Running cqlsh against cassandra 3 throws error about beta flag not set
• fixes: CASSANDRA-9362 Native protocol v5
• is duplicated by: CASSANDRA-16470 TestCqlsh.test_protocol_negotiation needs to be updated for v5
• relates to: CASSANDRA-16613 ProtocolVersion.V4 is still used in places in the code
• links to: JAVA-2704