cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christoph Hack (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2478) Custom CQL protocol/transport
Date Mon, 07 Nov 2011 21:04:52 GMT


Christoph Hack commented on CASSANDRA-2478:

I would really appreciate a such a custom protocol since I would like to write a Go client.

Go seems to be a bad fit for Thrift since the language and API is improving steadily (which
isn't a problem for Go programs, since there is a tool called "gofix" which is able to rewrite
existing code), but updating the code-generator for Thrift all the time is not practical.
Also, I do not want to contribute to Thrift at the moment and writing a generator to generate
non-idiomatic code instead of writing a nice API in the first place (without huge amounts
of duplicated generated code) seems like the better solution for me (but that's just my personal

I know, this feature was just proposed recently, but is it likely that it might be implemented
in the near future?
> Custom CQL protocol/transport
> -----------------------------
>                 Key: CASSANDRA-2478
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API, Core
>            Reporter: Eric Evans
>            Priority: Minor
>              Labels: cql
> 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