incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dong.yajun" <dongt...@gmail.com>
Subject Re: Cassandra - conflict resolution for column updates with identical timestamp
Date Sun, 24 Mar 2013 03:18:41 GMT
Thanks Capriolo,

Umm.. so is there any background or history abort this issue?

On Sun, Mar 24, 2013 at 2:32 AM, Edward Capriolo <edlinuxguru@gmail.com>wrote:

> The value that sorts higher, this way it is deterministic.
>
>
> On Sat, Mar 23, 2013 at 12:12 PM, dong.yajun <dongtalk@gmail.com> wrote:
>
>> Hello,
>>
>> I would like to know which write wins in case of two updates with the
>> same client timestamp in Cassandra.
>>
>> Initial data: KeyA: { col1:"val AA", col2:"val BB", col3:"val CC"}
>>
>> Client 1 sends update: KeyA: { col1:"val C1", col2:"val B1"} on Sx
>>
>> Client 2 sends update: KeyA: { col1:"val C2", col2:"val B2"} on Sy
>>
>> Both updates have the same timestamp.
>>
>> --
>> *Ric Dong*
>>
>>
>


-- 
*Ric Dong *
Newegg Ecommerce, MIS department

Mime
View raw message