It's always been like that see https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/Column.java#L231
Chees ----------------- Aaron Morton Freelance Cassandra Consultant New Zealand @aaronmorton http://www.thelastpickle.com On 24/03/2013, at 4:18 PM, dong.yajun <dongt...@gmail.com> wrote: > Thanks Capriolo, > > Umm.. so is there any background or history abort this issue? > > On Sun, Mar 24, 2013 at 2:32 AM, Edward Capriolo <edlinuxg...@gmail.com> > wrote: > The value that sorts higher, this way it is deterministic. > > > On Sat, Mar 23, 2013 at 12:12 PM, dong.yajun <dongt...@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 >
