News for hackers. Stuff that matters.

A comment on Cassandra is not row level consistent. Parent comment

Re:Cassandra is not row level consistent by mdani on Friday November 25, 2016 @12:11AM (#13034527)
The IF statement uses Paxos as underlying implementation and still it may result into an inconsistency if you are using two separate CQL statements. Cassandra does not provide begin ... end construction where everything is atomically committed or rolled back.
[ Parent | on HN ]
Re:Cassandra is not row level consistent by pkolaczk on Friday November 25, 2016 @07:46AM (#13036328)
You can use Cassandra LWT as a building block for multi-partition transactions, in a similar way like CAS atomic operations are used to build locks, mutexes and monitors and then monitors are used to implement ACID transactions in RDBMS. However, noone says it would be easy or performant, therefore this is probably not a good idea.
[ Parent | on HN ]
Re:Cassandra is not row level consistent by mdani on Sunday December 04, 2016 @01:24AM (#13099018)
Right. Cassandra crawled at 20 TPS when we sent IF cql statements. One thing to note is that Cassandra txns can never be rolled back - they can only be committed/ retrried and so on.
[ Parent | on HN ]