[
https://issues.apache.org/jira/browse/CASSANDRA-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13464921#comment-13464921
]
Sylvain Lebresne commented on CASSANDRA-4545:
---------------------------------------------
I'll reformulate: we don't want to completely refuse counters, at least not in
unlogged batches.
Sure batch of counters shouldn't be replay, but that's not a good reason to
refuse batches in the first place. Typically CASSANDRA-4723 exists exactly so
user can know it was a counter batch and should not be replay. Or to be more
precise, if you timeout with counters you're screwed, them being in batch or
not, so allowing batch of counters is not worst than allowing counters in the
first place, so why forbid them? Especially since with CQL3, you often have to
use a BATCH even to insert data in the same "Cassandra" row, and so disallowing
BATCH of counters would be a major regression compared to what you can do with
thrift.
It's true though that we need to decide if we allow the BEGIN BATCH for
counters, or only the BEGIN UNLOGGED BATCH one, or both. We could even say that
counter batch needs to use a specific syntax like BEGIN COUNTER BATCH. Given
that counter are a specific case anyway as far as failed write is concerned, I
think just allowing BEGIN BATCH would probably not be a big deal, though I do
kind of like the idea of a BEGIN COUNTER BATCH syntax as it highlight the fact
that counter and regular column cannot be mixed. I don't care too much one way
or the other.
> 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
> Attachments: CASSANDRA-4545.txt
>
>
> 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
