cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2478) Custom CQL protocol/transport
Date Fri, 18 May 2012 17:47:07 GMT


Yuki Morishita commented on CASSANDRA-2478:

Couple of comments on protocol proposal:

* Support for secure connection(SSL support) - we can implement this later, but I think it
is better to mention in protocol. Do we need to connect to secure port from the beginning
or we upgrade to SSL after handshake when server supports secure connection?
* READY messages body - We may want to reserve some space for server response (possibly, server
capabilities), using [option list]
* Types in metadata - proposal states it is sent in <string> format, but is it better
to use flags? When custom type is used, we can append FQCN of that type after the flag. 
> Custom CQL protocol/transport
> -----------------------------
>                 Key: CASSANDRA-2478
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API, Core
>            Reporter: Eric Evans
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>              Labels: cql
>         Attachments: cql_binary_protocol
> A custom wire protocol would give us the flexibility to optimize for our specific use-cases,
and eliminate a troublesome dependency (I'm referring to Thrift, but none of the others would
be significantly better).  Additionally, RPC is bad fit here, and we'd do better to move in
the direction of something that natively supports streaming.
> I don't think this is as daunting as it might seem initially.  Utilizing an existing
server framework like Netty, combined with some copy-and-paste of bits from other FLOSS projects
would probably get us 80% of the way there.

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