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

Michaël Figuière commented on CASSANDRA-4693:
---------------------------------------------

Considering the key role of Batches in CQL3, it would actually be very 
interesting to allow clients to send a list of both prepared and un-prepared 
statements to be executed with the same semantic and guarantees of a BATCH 
command. This would allow applications developers / frameworks to prepare most 
of their queries and include an additional one that is generated at runtime. An 
example of a use case that would leverage such is feature is when a bunch of 
columns need to be saved along with a set of complex collection mutations.
                
> 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

Reply via email to