On 9 June 2010 10:43, Sylvain Lebresne wrote:
> > However, as a final point of clarification, is there a particular reason
> > that insert does not raise an exception when trying to insert over an
> > existing key, or when the key points to a tombstone record ?
>
> Inserting over an existing key
address+timestamp, that sort of thing).
>>
>> For keys representing user accounts or something similar, I would
>> recommend
>> using an external synchronisation mechanism, because for actions like
>> account
>> registration latency caused by such a mechanism is usually n
ls [mailto:jool...@gmail.com]
Sent: Wednesday, June 09, 2010 11:09 AM
To: user@cassandra.apache.org
Subject: Re: Inserting new data, where the key points to a tombstone
record.
Hi Martin,
Many thanks for the succinct, and clear response.
ng in quickly, where the overhead of synchronisation is not
> acceptable,
> use the UUID variant and reconcile the data on read.
>
> HTH,
> Martin
>
> --
> *From:* Jools [mailto:jool...@gmail.com]
> *Sent:* Wednesday, June 09, 2010 10:39 AM
> *
use the UUID variant and reconcile the data on read.
HTH,
Martin
From: Jools [mailto:jool...@gmail.com]
Sent: Wednesday, June 09, 2010 10:39 AM
To: user@cassandra.apache.org
Subject: Inserting new data, where the key poin
Hi,
I've been developing a system against cassandra over the last few weeks, and
I'd like to ask the community some advice on the best way to deal with
inserting new data where the key is currently a tombstone record.
As with all distributed systems, this is always a tricky thing to deal with,
so
