cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-4453) Better support of collections in the binary protocol
Date Tue, 31 Jul 2012 15:03:35 GMT


Sylvain Lebresne updated CASSANDRA-4453:

    Attachment: 0002-Support-collections-natively-in-the-binary-protocol.txt

Attaching 2 patches for this. The first one adds the use of a simple binary encoding for the
collection for the binary protocol. But it also adds proper compose/decompose methods to the
collection types to make it more useful for java drivers.
The second patch makes collection native types for the binary protocol (i.e. it assign them
short ids like we do for other native types instead of serializing the full name of the comparator
in the metadata).

Note that I've kept json formalization for the thrift side (that's easier for the dtests right
now), but as said previously, we could use the binary encoding there too, it's not a lot more
complicated for clients.

> Better support of collections in the binary protocol
> ----------------------------------------------------
>                 Key: CASSANDRA-4453
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>    Affects Versions: 1.2
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>             Fix For: 1.2
>         Attachments: 0001-Adds-generics-to-collection-types.txt, 0002-Support-collections-natively-in-the-binary-protocol.txt
> Currently, collections results are serialized to json string and send that way. This
doesn't feel right at all for the binary protocol and we should use a simple binary serialization
of the collection instead.
> For the thrift protocol, we might want to keep the json serialization or use the same
binary serialization. I don't really have much opinion.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message