incubator-cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From paul cannon <pcan...@gmail.com>
Subject Re: Best place to discuss CQL Binary Protcol spec?
Date Tue, 19 Feb 2013 04:06:04 GMT
On Mon, Feb 18, 2013 at 6:48 PM, Michael Alan Dorman <
mdorman@ironicdesign.com> wrote:

> paul cannon <pcannon@gmail.com> writes:
>
> As the doc says, each <value_j> is a [bytes], which means it's represented
> > on the wire as an [int] x followed by x bytes.
>
> Thank you for pointing out what I had succeeded in reading repeatedly
> without actually processing. ;)
>
> At the same time, that seems to gloss over the structure of the
> content---it's not all encoded as string values, or is it?
>


No, the values are serialized according to whatever data type definitions
they have. The data types and serializations are technically details of
Cassandra usage in general (not specific to the native protocol), and the
types aren't limited to the ones which are assigned type IDs in the native
protocol, so it is arguably appropriate to leave out type serialization
details in the native protocol document (I could see it either way).

If you do need details, the builtin cassandra types and serialization
formats are defined in the various org.apache.cassandra.db.marshal.*Type
classes. Or read deserialization code from the other C* libraries.

p

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message