cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergio Bossa (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9515) Bytes map encoding does not match protocol spec
Date Mon, 01 Jun 2015 08:56:18 GMT


Sergio Bossa commented on CASSANDRA-9515:

I think using [bytes], that is, a null-allowing int length, would be safer in terms of general
protocol usability, and not much of a size waste.

> Bytes map encoding does not match protocol spec
> -----------------------------------------------
>                 Key: CASSANDRA-9515
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Olivier Michallat
>            Assignee: Robert Stupp
> 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.

This message was sent by Atlassian JIRA

View raw message