Yes i have done a mistake I know ! But I hoped nobody would notice :).
It is the odds of winning 3 days in a row (standard probability fail). Still
it is totally unlikely
Sorry about this mistake,
Best regards,
Victor K.
brendan.po...@new-law.co.uk
029 2078 4283
www.new-law.co.uk
From: Kallin Nagelberg [mailto:kallin.nagelb...@gmail.com]
Sent: 08 February 2011 03:38
To: user@cassandra.apache.org
Subject: Re: unique key generation
Pretty sure it also uses mac address, so
Pretty sure it also uses mac address, so chances are very slim. I'll check
out time uuid too, thanks.
On 7 Feb 2011 17:11, "Victor Kabdebon" wrote:
Hello Kallin.
If you use timeUUID the chance to generate two time the same uuid is the
following :
considering that both client generate the uuid at
If you are a Hector user, TimeUUIDUtils can be used to create Time UUIDs.
https://github.com/rantav/hector/blob/master/core/src/main/java/me/prettyprint/cassandra/utils/TimeUUIDUtils.java
On Mon, Feb 7, 2011 at 2:11 PM, Kallin Nagelberg wrote:
> Maybe I can just use java5's UUID.. Need to rese
Maybe I can just use java5's UUID.. Need to research how this is
effective across multiple clients..
On Mon, Feb 7, 2011 at 4:57 PM, Kallin Nagelberg
wrote:
> Hey,
>
> I am developing a session management system using Cassandra and need
> to generate unique sessionIDs (cassandra columnfamily keys
Hello Kallin.
If you use timeUUID the chance to generate two time the same uuid is the
following :
considering that both client generate the uuid at the *same millisecond*,
the chance of generating the same uuid is :
1/1.84467441 × 1019Which is equal to the probability for winning a national
lotte
