[
https://issues.apache.org/jira/browse/CASSANDRA-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182654#comment-13182654
]
Jonathan Ellis commented on CASSANDRA-2478:
-------------------------------------------
bq. I believe the focus is on getting CQL up to 100% parity functionality-wise
with Thrift, and then there will be time to work on this.
The end is in sight (CASSANDRA-2474 is almost done, with CASSANDRA-2477 to
follow soon), so I agree that it's time to start thinking harder about this.
Are there any serious contenders besides HTTP and a simple custom protocol
similar to the one outlined by Rick? Hessian looks a lot more like Thrift than
like something we'd use here.
> Custom CQL protocol/transport
> -----------------------------
>
> Key: CASSANDRA-2478
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2478
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
