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
Note also (though you are likely not hitting them) there were a bunch of static
column related edge cases fixed in 2.0.10
On Sep 7, 2014, at 1:18 PM, graham sanderson wrote:
> Presumably you meant unread_ids to be a static column (it isn’t in your table
> definition)
>
> On Sep 7, 2014, at 10
Presumably you meant unread_ids to be a static column (it isn’t in your table
definition)
On Sep 7, 2014, at 10:14 AM, tommaso barbugli wrote:
> Hi,
> I am trying to use a couple of static columns; I am using cassandra 2.0.7 and
> when I try to set a value using the partition key only, I get a
Hi,
I am trying to use a couple of static columns; I am using cassandra 2.0.7
and when I try to set a value using the partition key only, I get a primary
key incomplete error.
Here is the schema and the query with the error I get from cqlsh
CREATE TABLE shard75 (
group_id ascii,
event_id time
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
