[
https://issues.apache.org/jira/browse/CASSANDRA-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455067#comment-13455067
]
Sylvain Lebresne commented on CASSANDRA-4545:
---------------------------------------------
What would be really nice though to make that decision would be to have a few
benchmarks to estimate how much of an impact it is exactly.
And on the one side, if we ship that for 1.2, CQL3 is basically new (as in, it
was beta in 1.1), so if we want to make it the default, we should do it now or
never.
I guess in an ideal world I'd prefer having the safer option be the default,
but I can agree with the "unpleasant surprise" argument and I'd probably be
fine with a syntax like:
{noformat}
BEGIN ATOMIC BATCH
{noformat}
to use batchlog. The only slight downside is that this could lead people to
believe that if they want a single insert to be atomic, they might need to put
it in an atomic batch.
> 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
