cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2478) Custom CQL protocol/transport
Date Fri, 06 Jul 2012 15:41:36 GMT


Sylvain Lebresne commented on CASSANDRA-2478:

bq. Do you expect the spec to be implemented "by hand"?

That's what I would do but everybody is free to do whatever he prefers :)

bq. I don't see too many people writing their own generators

That's likely true but I personally don't see that as a show stopper. In my ideal world, what
I would like to see is 1 good implementation (of the protocol) per language that everyone
reuse. Now, yeah it's unlikely COBOL will get such good implementation soon, but I can live
with that. 

bq. it should be possible to verify (not "test", verify) a driver for compliance

Sure, it would be nice. I'd lie if I said this is a priority on my todo list at this stage,
but I would certainly welcome such a contribution.

> 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
>             Fix For: 1.2
>         Attachments: cql_binary_protocol, cql_binary_protocol-v2
> 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