[
https://issues.apache.org/jira/browse/CASSANDRA-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461874#comment-13461874
]
Jonathan Ellis commented on CASSANDRA-4545:
-------------------------------------------
I think I would favor {{BEGIN BATCH}} for atomic and {{BEGIN UNLOGGED BATCH}}
otherwise. Reasoning:
# I'm pessimistic that people will (a) understand the {{ATOMIC|NONATOMIC}}
distinction without (b) being needlessly scared. Doing the "right" thing by
default means we don't have to inflict a decision on new users that they're not
yet qualified to make.
# Secondarily, this is a gentler "breaking" of your code (for hypothetical cql3
1.1 users) vs making {{BEGIN BATCH}} not work without a qualifier. If someone
upgrading from cql3 in 1.1 notices the slowdown (or reads NEWS) they can switch
to {{UNLOGGED}} if they want. Granted, we explicitly said cql3 in 1.1 is beta,
but if we can avoid breaking things, so much the better.
I don't have a good answer for the "someone could compare Thrift
{{batch_mutate}} with 1.2 {{BEGIN BATCH}} without noticing that it really
corresponds to {{atomic_batch_mutate}}" concern, other than that I'm willing to
live with that price.
> 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
>
> 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
