[
https://issues.apache.org/jira/browse/CASSANDRA-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932187#action_12932187
]
Eric Evans commented on CASSANDRA-1703:
---------------------------------------
bq. I generally like this proposal, except I don't think we should get rid of
the rpc methods.
Just to be clear, the RPC methods I'm referring to here are the Avro RPC
methods (not Thrift).
bq. Sometimes the performance will be worth it (assuming that the direct rpc
will be faster, which seems to be a safe assumption).
The back-of-napkin tests I've done so far put CQL and Thrift on even footing,
and there is a _ton_ of room for improvement on the CQL-side (ditching the HTTP
transport for example). Proper benchmarks need to be done to be sure, but I'm
operating on the assumption that greater-than or equal-to performance is
possible.
> CQL 1.0
> -------
>
> Key: CASSANDRA-1703
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1703
> Project: Cassandra
> Issue Type: New Feature
> Components: API
> Affects Versions: 0.8
> Reporter: Eric Evans
> Priority: Minor
> Fix For: 0.8
>
>
> CQL (Cassandra Query Language) is a proposed language for data management in
> Cassandra.
> This issue is meant to encapsulate the goals for CQL in the next stable
> release (0.8), roughly:
> * Completed 1.0 language specification.
> * Implementation of the language using the Avro interface for transport and
> serialization.
> * Low-level drivers for Java and Python (possibly others).
> * The deprecation (or removal, TBD) of (Avro) RPC methods.
> Separate tickets with the appropriate relationships to this one will be
> created for the individual tasks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
