cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4545) add cql support for batchlog
Date Thu, 27 Sep 2012 19:51:07 GMT

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

Sylvain Lebresne commented on CASSANDRA-4545:
---------------------------------------------

bq. Why is that? Can't I write UPDATE foo SET x = x + 1, y = y + 2, ... ?

Sure you can, but that only works for columns in the same "CQL" row. If you have a wide row
(a.k.a a composite PK), you can't update multiple ones without a BATCH (and for *the* good
use case of counters, realtime analytics, doing time series of counter is really useful).
And without a BATCH, you do lose the atomicity and isolation we currently have in that case
(on top of the performance penalty).

bq. to give people a gun to shoot their feet with

I'm not sure I understand why that's so much a "gun to shoot their feet with". As far as I
can tell, allowing counter batches adds no foot shooting over allowing counters (which have
by themsleves some foot shooting involved, but that's another problem). You should not replay
counter inserts, but whether they are in batch or not don't make a whole of a difference (in
both case you don't know what insert went in or not).
                
> add cql support for batchlog
> ----------------------------
>
>                 Key: CASSANDRA-4545
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4545
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Jonathan Ellis
>            Assignee: Aleksey Yeschenko
>         Attachments: CASSANDRA-4545.txt
>
>
> Need to expose the equivalent of atomic_batch_mutate (CASSANDRA-4542) to CQL3.

--
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

Mime
View raw message