cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4693) CQL Protocol should allow multiple PreparedStatements to be atomically executed
Date Sat, 25 May 2013 00:47:21 GMT


Aleksey Yeschenko commented on CASSANDRA-4693:

- 4.1.9 BATCH section number is wrong -> should be 4.1.7
- QueryProcessor.processBatch() should call checkAccess() first, then validate() - to avoid
leaking info on keyspace/tables existence to unauthenticated users
- BatchMessage.toType() has an error: 2 should map to COUNTER, not to UNLOGGED

Other than that LGTM
> 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