Hi Maifi,

This is the expected behaviour for updating a value - the "newest" value
always wins in the event of a conflict (e.g. after two partitions converge).

Your use case is that of incrementing counters, which is not something that
is easily solved in Cassandra at the moment.

There are issues currently logged for counters (and version vectors, which
are loosely related):

   - https://issues.apache.org/jira/browse/CASSANDRA-1072 - Increment
   Counters
   - https://issues.apache.org/jira/browse/CASSANDRA-580 - Version Vectors

Also, this is really something for the user list (u...@cassandra.apache.org)

Regards,
Nick

Reply via email to