A slight correction/clarification:
1) DeletedColumns always win. If there are two deletes the highest timestamp
wins
DeletedColumns only take precedence over a normal value if they have a
greater *(or equal)* timestamp. *DeletedColumns always win* is only true
if you're talking about two
yup, my bad.
A
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 3 Aug 2011, at 19:45, Sam Overton wrote:
A slight correction/clarification:
1) DeletedColumns always win. If there are two deletes the highest timestamp
wins
What happens when DC is in different time zone so 9:00 pacific vs 11:00
Central
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Question-about-eventually-consistent-in-Cassandra-tp6646430p6649490.html
Sent from the cassandra-u
Hi,
Let’s say that I have 2 datacenters, a key is changed on both of my
datacenters in the exact same time (even in 1-2 seconds diff).
Datacenter #1 add column abc with value X Datacenter #2 add column abc
with value Y.
What is the result of that situation?
Is there any different if the changes
Have not used Cassandra much yet, but it seems pretty clear to me that the
entry with the latest timestamp (sent in by the client) will be the one that
will be the winner eventually.
Mark here that this is the timestamp the client send in which is not
necessarily the actual time.
So eg if the
is canonical. What would happen
if you make conflicting changes with the exact same time stamp? No idea.
- Original Message -
From: Eldad Yamin elda...@gmail.com
To: user@cassandra.apache.org
Sent: Tuesday, August 2, 2011 8:58:23 PM
Subject: Question about eventually consistent in Cassandra
Hi
with the exact same time stamp?
No idea.
- Original Message -
From: Eldad Yamin elda...@gmail.com
To: user@cassandra.apache.org
Sent: Tuesday, August 2, 2011 8:58:23 PM
Subject: Question about eventually consistent in Cassandra
Hi,
Let’s say that I have 2 datacenters, a key is changed