[CASSANDRA-14716] Protocol frame checksumming options should not be case sensitive

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.0-alpha1, 4.0
• Component/s: Legacy/CQL
• Severity: Normal
• Assignee: Sam Tunnicliffe
• Reporter: Sam Tunnicliffe

Authors

Sam Tunnicliffe

Reviewers

Aleksey Yeschenko

• Created: 11/Sep/18 15:52
• Updated: 15/May/20 08:02
• Resolved: 27/Nov/18 14:22

Description

Protocol v5 adds support for checksumming of native protocol frame bodies. The checksum type is negotiated per-connection via the STARTUP message, with two types currently supported, Adler32 and CRC32. The mapping of the startup option value requested by the client to a ChecksumType should not be case sensitive, but currently it is.