[ https://issues.apache.org/jira/browse/CASSANDRA-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280986#comment-13280986 ]
Rick Shaw commented on CASSANDRA-2478: -------------------------------------- Please consider returning the KS (schema) and CF (table) in the metadata returned with "rows" and a "prepare". This will facilitate clients reporting this information in metadata commands from the client side for tools and the like. This information can not really be known without the fragile method of scanning the CQL because the context is always passed withing the script itself. And with the addition of "KS.CF" notation in CQL for the selected CF you can't really use the state of a USE to tell what the applicable KS is within the currently returned information. > 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 > > > 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