UPDATE foo SET x = x + 1
is inherently not idempotent. Thus, client-based idempotence is not in
fact a design goal.
What 2.1 achieves is making commitlog replay idempotent.
On Fri, Oct 10, 2014 at 3:44 AM, Rajath Subramanyam
wrote:
> Hi Aleksey,
>
> Thanks for the response. I read through sev
Hi Aleksey,
Thanks for the response. I read through several JIRAs ( CASSANDRA-1072,
CASSANDRA-2495, CASSANDRA-4775, CASSANDRA-6504, CASSANDRA-6506). I would
appreciate if you can clarify my understanding of the current state of art.
I understand that the earlier design of having local shards, rem
No, there are no unique ids per increment. That was one of the ideas suggested
in https://issues.apache.org/jira/browse/CASSANDRA-4775, but ultimately
declined.
Read that ticket, and the one linked to it, for details.
--
AY
On October 6, 2014 at 10:20:05 PM, Rajath Subramanyam (rajat...@gmail
Hi Cassandra developers,
I am working on a project to make counter updates idempotent. I read that
via CASSANDRA-1546 assigns unique marker ids to counter updates in 0.7.1.
Does this unique marker id hold true in the later versions too ? Or at
least in 0.8.1 ?
Please let me know.
Thank you !
Re
