You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2012/09/20 16:47:07 UTC

[jira] [Commented] (CASSANDRA-4693) CQL Protocol should allow multiple PreparedStatements to be atomically executed

    [ https://issues.apache.org/jira/browse/CASSANDRA-4693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13459638#comment-13459638 ] 

Sylvain Lebresne commented on CASSANDRA-4693:
---------------------------------------------

One way to allow that would be to allow for the executePrepared message of the protocol to take a list of (preparedId, values) instead of just one (we would obviously refuse the query if the list size is > 1 and there is something else than a modification statement). Not sure we want to bother with on the CQL-over-thrift side however (I don't).
                
> CQL Protocol should allow multiple PreparedStatements to be atomically executed
> -------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-4693
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4693
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Michaël Figuière
>              Labels: cql, protocol
>
> Currently the only way to insert multiple records on the same partition key, atomically and using PreparedStatements is to use a CQL BATCH command. Unfortunately when doing so the amount of records to be inserted must be known prior to prepare the statement which is rarely the case. Thus the only workaround if one want to keep atomicity is currently to use unprepared statements which send a bulk of CQL strings and is fairly inefficient.
> Therefore CQL Protocol should allow clients to send multiple PreparedStatements to be executed with similar guarantees and semantic as CQL BATCH command.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira