[CASSANDRA-9515] Bytes map encoding does not match protocol spec

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.2.0 rc1
• Component/s: Legacy/CQL
• Severity: Normal
• Since Version: 2.2.0 beta 1
• Assignee: Benjamin Lerer
• Reporter: Olivier Michallat

Authors

Benjamin Lerer

Reviewers

Sylvain Lebresne

• Created: 29/May/15 19:44
• Updated: 16/Apr/19 09:31
• Resolved: 02/Jun/15 13:36

Description

In native_protocol_v4.spec, [bytes map] is defined as having [bytes] values, where [bytes] is an int n followed by n bytes.

In practice, CBUtil#writeBytesMap encodes each value with CBUtil#writeBytes, which writes the length as a short (so a [short bytes] instead of a [bytes]).

This is used for the custom payload introduced by CASSANDRA-8553.

Issue Links

• relates to: CASSANDRA-8553 Add a key-value payload for third party usage