> Always specify some constant value for timestamp. Only 1st insertion with that
> timestamp will succeed. Others will be ignored, because will be considered
> duplicates by cassandra.
Just be aware that this limits you in several ways in terms of your
data model. For examle, if you ever need to r
Reverse timestamp.
-Original Message-
From: Sylvain Lebresne [mailto:sylv...@yakaz.com]
Sent: Tuesday, October 19, 2010 10:44 AM
To: user@cassandra.apache.org
Subject: Re: Preventing an update of a CF row
> Always specify some constant value for timestamp. Only 1st insertion with t
> Always specify some constant value for timestamp. Only 1st insertion with that
> timestamp will succeed. Others will be ignored, because will be considered
> duplicates by cassandra.
Well, that's not entirely true. When cassandra 'resolves' two columns
having the
same timestamp, it will compare
Nice and simple!
-Original Message-
From: Oleg Anastasyev [mailto:olega...@gmail.com]
Sent: Tuesday, October 19, 2010 9:00 AM
To: user@cassandra.apache.org
Subject: Re: Preventing an update of a CF row
kannan chandrasekaran yahoo.com> writes:
> Hi All,I have a query regardi
kannan chandrasekaran yahoo.com> writes:
> Hi All,I have a query regarding the insert operation. The insert operation by
default inserts an new row or updates an existing row. Is it possible to
prevent an update but allow only inserts automatically ( especially when
multiple clients are writing
> I have a query regarding the insert operation. The insert operation by
> default inserts an new row or updates an existing row. Is it possible to
> prevent an update but allow only inserts automatically ( especially when
> multiple clients are writing to cassandra)? I was wondering if there is
