You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@cassandra.apache.org by Aaron Morton <aa...@thelastpickle.com> on 2010/07/14 23:54:23 UTC

timestamps and batch_mutation

Is it OK or recommended to use the same timestamp value for all Column and Deletion records sent in a batch mutation?

Am thinking of cases where there is a potential for multiple clients to update the same key (with multiple columns) at the same time. In the use case it's acceptable, as the client software is responsible for coordination. I just want to ensure there is consistency with regard to one update winning.

Thanks
Aaron

Re: timestamps and batch_mutation

Posted by Jonathan Ellis <jb...@gmail.com>.

It is good style but may not be necessary.

On Wed, Jul 14, 2010 at 4:54 PM, Aaron Morton <aa...@thelastpickle.com> wrote:
> Is it OK or recommended to use the same timestamp value for all Column and
> Deletion records sent in a batch mutation?
>
> Am thinking of cases where there is a potential for multiple clients to
> update the same key (with multiple columns) at the same time. In the use
> case it's acceptable, as the client software is responsible for
> coordination. I just want to ensure there is consistency with regard to one
> update winning.
>
> Thanks
> Aaron
>
>



-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of Riptano, the source for professional Cassandra support
http://riptano.com