"user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Date: Monday, November 16, 2015 at 4:05 PM
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Re: Overri
on behalf of Jon Haddad <
> j...@jonhaddad.com>
> Reply-To: "user@cassandra.apache.org"
> Date: Monday, November 16, 2015 at 4:05 PM
> To: "user@cassandra.apache.org"
> Subject: Re: Overriding timestamp with light weight transactions
>
> LWT uses the coordinat
he.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Re: Overriding timestamp with light weight transactions
LWT uses the coordinator's machine's timestamp to generate a timeuuid, which is
used as the timestamp of the paxos ballot. You
ssandra.apache.org <mailto:user@cassandra.apache.org>"
> mailto:user@cassandra.apache.org>>
> Subject: Re: Overriding timestamp with light weight transactions
>
> Perhaps you should fix your clock drift issues instead of trying to use a
> workaround?
>
>&g
er@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Date: Monday, November 16, 2015 at 3:42 PM
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Re: Overriding t
Perhaps you should fix your clock drift issues instead of trying to use a
workaround?
> On Nov 16, 2015, at 11:39 AM, Peddi, Praveen wrote:
>
> Hi,
> We are using Cassandra 2.0.9 and we currently have “using timestamp” clause
> in all our update queries. We did this to fix occasional issues wi
