You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2013/05/22 00:28:20 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=13663492#comment-13663492 ] 

Aleksey Yeschenko commented on CASSANDRA-4693:
----------------------------------------------

Could you rebase? It no longer applies because of trigger changes to BatchStatement.
                
> 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
>            Assignee: Sylvain Lebresne
>              Labels: cql, protocol
>             Fix For: 2.0
>
>         Attachments: 0001-Binary-protocol-adds-message-to-batch-prepared-or-not-.txt
>
>
> 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