Thanks, that makes more sense now.
On September 7, 2014 at 5:57:03 AM, Ian Rose (ianr...@fullstory.com) wrote:
I assume it's a hash to detect read/write races. As an example:
1. actor 1 reads key = (1, 'whatever') and gets value = V0
2. actor 2 writes to key (1, 'whatever') with new value V1
3
I assume it's a hash to detect read/write races. As an example:
1. actor 1 reads key = (1, 'whatever') and gets value = V0
2. actor 2 writes to key (1, 'whatever') with new value V1
3. actor 1 writes an anticolumn with key = (0, 'whatever') and value =
md5(V0)
4. later, if someone wants to read t
So I watched Instagram’s presentation about Cassandra and how they handle
undos/deletes (http://youtu.be/xDtclzE4ydA?t=12m55s) and how to get around the
race condition that a get-before-write causes.
They use this anti-column that stores an action where the first component of
the composite co
