[
https://issues.apache.org/jira/browse/CASSANDRA-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13457049#comment-13457049
]
Sylvain Lebresne commented on CASSANDRA-4545:
---------------------------------------------
bq. maybe it's simpler to just say "clients should be responsible for this
optimization" in the first place
I disagree. I don't want user to be like "Hum, I know I need atomicity for that
query but wait ... I'm only writing to one partition key so I'd better not use
the ATOMIC keyword in my query because that's slower and those lazy C* devs
didn't bother adding a one line 'if' to optimize the atomic path. Oh, and wait,
I'd better add a comment that this needs to be atomic since someone else
reading my query would think it's not required".
Besides, the details of when to retry should hopefully largely be hidden by the
client library, but that optimization cannot, or at least not easily as this
would require parsing the query.
> 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
