[
https://issues.apache.org/jira/browse/CASSANDRA-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461803#comment-13461803
]
Sylvain Lebresne commented on CASSANDRA-4545:
---------------------------------------------
Ok, so atomic batches are noticeably slower than non atomic ones. Can't say
it's a big surprise but it's nice to some numbers at least.
Tbh I don't have a strong conviction on what is the best solution here. On the
one side, I like the idea of having all our write operations being atomic by
default and I think ideally they should be. On the other side, I know that if
we use atomic by default, since it's slower, a fair amount of people that
upgrade to CQL3 will conclude that "CQL3 is slower than thrift" without looking
further. And I wouldn't totally blame them.
In that context I don't dislike the option of making the choice explicit in the
syntax (i.e. allowing 'BEGIN ATOMIC BATCH' and 'BEGIN NON-ATOMIC BATCH' but
not 'BEGIN BATCH'), but that would be one more syntax breaking change in CQL3
we make fairly late before the release, which is not ideal. Might still be my
slightly prefered choice at this point, but again, not a very strong conviction.
> 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
