Re: TimeUUID

[Dave Brosius]

Given that these rows are wanted to be time buckets, you would want collisions, in fact that would be the standard way of working, so IMO, the uuid just removes the ability to bucket data and would not be wanted. On 02/28/2012 10:30 AM, Paul Loy wrote: In a multi server env, to avoid key collisions timeuuid may be the better choice. On Monday, February 27, 2012, Tamar Fraenkel wrote: Hi! I have a column family where I use rows as "time buckets".  What I do is take epoc time in seconds, and round it to 1 hour (taking the result of time_since_epoc_second divided by 3600). My key validation type is LongType. I wonder whether it is better to use TimeUUID or even readable string representation for time? Thanks, -- Tamar Fraenkel  Senior Software Engineer, TOK Media  ta...@tok-media.com Tel:   +972 2 6409736  Mob:  +972 54 8356490  Fax:   +972 2 5612956    -- Sent from my iPhone, sorry for my brevity.