ok got it. So, only using LWT txn the updates across nodes for a particular
row can be isolated, so basically paxos would ensure serializable isolation
Thanks,
Rajesh
On Wed, May 16, 2018 at 4:56 PM, kurt greaves wrote:
> Atomicity and isolation are only guaranteed within a replica. If you hav
Atomicity and isolation are only guaranteed within a replica. If you have
multiple concurrent requests across replicas last timestamp will win. You
can get better isolation using LWT which uses paxos under the hood.
On 16 May 2018 at 08:55, Rajesh Kishore wrote:
> Hi,
>
> I am just curious to kn
Hi,
I am just curious to know when Cassandra doc says the atomicity and
isolation is guaranteed for a row.
Does it mean, two requests updating a row- "R1" at different replica will
be candidate for atomicity and isolation?
For instance , I have a setup where RF is 2
I have a client application wh
