[
https://issues.apache.org/jira/browse/CASSANDRA-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455091#comment-13455091
]
Aleksey Yeschenko commented on CASSANDRA-4545:
----------------------------------------------
We can create two versions - BEGIN .. APPLY ATOMICALLY and BEGIN .. APPLY
NON-ATOMICALLY (or BEGIN NON-ATOMIC BATCH and BEGIN ATOMIC BATCH), or some
better names. This comment is not about names.
And leave the BEGIN .. APPLY syntax. Make a setting in cassandra.yaml that
would determine how to treat BEGIN .. BATCH statements - as atomic or
non-atomic. And make atomic the default.
Upgraders without the setting will get the old behaviour - no atomicity, no
unpleasant surprises. New users will get atomicity by default, which, I agree,
is a better default.
Having two versions of the statement will also allow users let users to choose
on per-query basis, without changing any settings.
> 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
