[
https://issues.apache.org/jira/browse/CASSANDRA-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025253#comment-13025253
]
Pavel Yaskevich commented on CASSANDRA-2537:
--------------------------------------------
Yes, I know that - it's changed in CASSANDRA-2553 as I didn't want to touch
QP.batchUpdate before moving UpdateStatement to use multiple keys...
> CQL: Support for batch insert/delete
> ------------------------------------
>
> Key: CASSANDRA-2537
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2537
> Project: Cassandra
> Issue Type: New Feature
> Affects Versions: 0.8 beta 1
> Environment: 3-node Centos 5.5 cluster running 0.8 build from apr20.
> Reporter: Cathy Daw
> Assignee: Pavel Yaskevich
> Priority: Minor
> Labels: cql
> Fix For: 0.8.1
>
> Attachments: CASSANDRA-2537-v2.patch, CASSANDRA-2537-v3.patch,
> CASSANDRA-2537-v4.patch, CASSANDRA-2537.patch
>
>
> *Test Case To Run*
> {code}
> // Setup
> CREATE COLUMNFAMILY users (
> KEY varchar PRIMARY KEY,
> password varchar);
> //Batch Insert
> BEGIN BATCH USING QUORUM
> INSERT INTO users (KEY, password) VALUES ('user2', 'ch@ngem3b');
> INSERT INTO users (KEY, password) VALUES ('user3', 'ch@ngem3c');
> APPLY BATCH
> {code}
> *Actual Behavior*
> {code}
> cqlsh> BEGIN BATCH USING QUORUM
> ... INSERT INTO users (KEY, password) VALUES ('user2', 'ch@ngem3b');
> Bad Request: line 0:-1 mismatched input '<EOF>' expecting K_APPLY
> {code}
> *Documentation Sample*
> {code}
> BEGIN BATCH [USING <CONSISTENCY>]
> UPDATE CF1 SET name1 = value1, name2 = value2 WHERE KEY = keyname1;
> UPDATE CF1 SET name3 = value3 WHERE KEY = keyname2;
> UPDATE CF2 SET name4 = value4, name5 = value5 WHERE KEY = keyname3;
> APPLY BATCH
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
