Hello Daniel,
That is correct this is for user creation and collisions should be rare. Is
the astyanax recipe a distributed lock? I do not understand what you mean
by a combination of reads and writes?
We are using cql3 with the Datastax java driver
Thanks
*From: *Daniel Chia
*Sent: *Tuesday,
Thanks again Michael. Those are the conclusions that I came to as well. For us
the window is small for possible duplicate users so I think we will have to do
the read before like you suggested. We will also have to be able to handle the
case where the duplicate users exist.
And thanks for the
BlackBerry 10 smartphone on the Rogers network.
Original Message
From: Michael Shuler
Sent: Monday, February 24, 2014 10:17 PM
To: user@cassandra.apache.org
Reply To: user@cassandra.apache.org
Subject: Re: Cassandra Data Model and Surrogate Keys
On 02/24/2014 09:00 PM, John Stager wrote:
> He
Hello,
We are working on our data model for Cassandra and we have a need to use
surrogate keys (timeuuid) and not the natural key for one of our tables but
this causes a possible timing issue when determining if a row already
exists.Are there any best practices or patterns for Cassandra for using
