Jacques-Henri Berthemet
>
> From: Rajesh Kishore [mailto:rajesh10si...@gmail.com]
> Sent: Thursday, June 21, 2018 7:45 AM
> To: user@cassandra.apache.org
> Subject: Re: how to avoid lightwieght transactions
>
> Hi,
>
> I think LWT feature is introduced for your kind of
From: Rajesh Kishore [mailto:rajesh10si...@gmail.com]
Sent: Thursday, June 21, 2018 7:45 AM
To: user@cassandra.apache.org
Subject: Re: how to avoid lightwieght transactions
Hi,
I think LWT feature is introduced for your kind of usecases only - you don't
want other requests to be updating the
Hi,
I think LWT feature is introduced for your kind of usecases only - you
don't want other requests to be updating the same data at the same time
using Paxos algo(2 Phase commit).
So, IMO your usecase makes perfect sense to use LWT to avoid concurrent
updates.
If your issue is not the concurren
Hi all,
we have a use case where we need to update frequently our rows. Now in
order to do so and so that we dont override updates we have to resort to
lightweight transactions.
Since lightweight is expensive(could be 4 times as expensive as normal
insert) , how do we model around it.
e.g i have a
