[ https://issues.apache.org/jira/browse/CASSANDRA-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407235#comment-13407235 ]
Sylvain Lebresne commented on CASSANDRA-2478: --------------------------------------------- bq. Here, I mean automated protocol test using SimpleClient in unit test. Oh ok. I was confused because the CliTest itself won't work (and will never) with the native protocol since it's completely thrift related. But yes, having some unit test can never hurt. Another avenue for tests will be to update the python cql driver to use the native transport, and then we'll be able to reuse the dtests (which have quite a bunch of CQL tests). bq. @Yuki I think everything is ok.. Let me do a final review cycle today again Ok. I will commit to trunk. We can always commit improvements later anyway (Norman: if you do spot some minor things, do feel free to comment on that ticket directly (or on github), even if it's closed, and I'll commit the changes). > 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 > Assignee: Sylvain Lebresne > Priority: Minor > Labels: cql > 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira