Thank you, JH.
I took a look and probably understand it.
Maybe, in summary,
if all the operations are LWT, there is no issue even if clocks are
drifted, because it's ballot based.
But, if some of the operations are non-LWT and clocks are drifted,
there might be causing issues.
(like overwriting
If you check the Jira issue I linked you'll see a recent comment describing a
potential explanation for my mixed LWT/non-LWT problem. So, it looks like there
can be some edge cases.
I'd say that if data was inserted a while ago (seconds) there should be no
problems.
--
Jacques-Henri Berthemet
Thank you JH.
But, it's still a little bit unclear to me
Let me clarify the question.
What I wanted to know is whether or not linearizability is sustained
by doing LWT (Consistency: QUORUM, Serial Consistency: SERIAL) on
data previously mutated by non-LWT (Consistency: QUORUM).
I think It should
Hi Hiroyuki,
For both operations you'll have to provide partition key so "conflict" at DB
level can always be resolved.
But if two operations, LWT and non-LWT, are racing against each others the
result is unpredictable, if non-LWT is applied after LWT the result will be
overwritten.
It
