Hi Daniel,
What is the RF and CL for Delete?Are you using asynchronous writes?Are you
firing both statements from same node sequentially?Are you firing these queries
in a loop such that more than one delete and LWT is fired for same partition?
I think if you have the same client executing both st
Daniel,
Cassandra is "eventually consistent". This means that the DELETE can go to
a different coordinator than the INSERT... IF NOT EXISTS. Being so, each
coordinator enters a race condition than can make the INSERT...IF NOT
EXISTS failed reading data that the DELETE will destroy. Even on the sam
The document explains you cannot mix them
http://docs.datastax.com/en/archived/cassandra/2.2/cassandra/dml/dmlLtwtTransactions.html
But what happens under the hood if I do? e.g,
DELETE
INSERT ... IF NOT EXISTS
The coordinator has 4 steps to do the second statement (INSERT)
1. prepare/promis
