3 ms·
In Cassandra the second update agreed upon by the cluster would "win", so either (X1,Y1) or (X2,Y2). Since there is no clock mechanism there is no way for the c
by brown9-2 13y ago
In Cassandra the second update agreed upon by the cluster would "win", so either (X1,Y1) or (X2,Y2). Since there is no clock mechanism there is no way for the cluster to see that the data has changed since the requester decided it wanted to update the value.
- rdtsc 13y agoBut didn't the article say that last update to column wins. To me it seems if X and Y values are in different columns you would end up with invalid data. Someone else (a sibling comment) pointed me out to row level locks. That is what I was wondering about. I am looking at that at the moment.
- aphyr 13y agoRows are not isolated. You might see (X1, Y1), (X1, Y2), (X2, Y1), or (X2, Y2) if timestamps happen to conflict. https://gist.github.com/aphyr/6402464 https://gist.github.com/aphyr/6402464
- brown9-2 13y agoOh wow, that is bad. I was assuming that guarantee of row isolation was valid.