cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-4693) CQL Protocol should allow multiple PreparedStatements to be atomically executed
Date Thu, 16 May 2013 14:59:17 GMT


Sylvain Lebresne updated CASSANDRA-4693:

    Attachment: 0001-Binary-protocol-adds-message-to-batch-prepared-or-not-.txt

Attaching patch for this. This adds a new BATCH message to the protocol that allows pass a
list of either string query (+ optional variables for one-shot binding) or prepared statement
id + variables, and batch all of this server side.

I made a small manual test and that seems to work correctly.
> CQL Protocol should allow multiple PreparedStatements to be atomically executed
> -------------------------------------------------------------------------------
>                 Key: CASSANDRA-4693
>                 URL:
>             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:

View raw message