You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Tamar Fraenkel <ta...@tok-media.com> on 2012/02/28 07:24:48 UTC
TimeUUID
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
[image: Inline image 1]
tamar@tok-media.com
Tel: +972 2 6409736
Mob: +972 54 8356490
Fax: +972 2 5612956
Re: TimeUUID
Posted by Dave Brosius <db...@mebigfatguy.com>.
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
>
> Inline image 1
>
> tamar@tok-media.com <javascript:_e({}, 'cvml',
> 'tamar@tok-media.com');>
> Tel: +972 2 6409736
> Mob: +972 54 8356490
> Fax: +972 2 5612956
>
>
>
>
>
> --
> Sent from my iPhone, sorry for my brevity.
Re: TimeUUID
Posted by Paul Loy <ke...@gmail.com>.
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
>
> [image: Inline image 1]
>
> tamar@tok-media.com <javascript:_e({}, 'cvml', 'tamar@tok-media.com');>
> Tel: +972 2 6409736
> Mob: +972 54 8356490
> Fax: +972 2 5612956
>
>
>
>
--
Sent from my iPhone, sorry for my brevity.
Re: TimeUUID
Posted by Tamar Fraenkel <ta...@tok-media.com>.
Thanks, makes my life easier.
Tamar
On Tue, Feb 28, 2012 at 10:23 AM, aaron morton <aa...@thelastpickle.com>wrote:
> not a great deal of difference, personally I would stick with seconds
> since epoch (it is probably slightly faster).
>
> Cheers
>
> -----------------
> Aaron Morton
> Freelance Developer
> @aaronmorton
> http://www.thelastpickle.com
>
> On 28/02/2012, at 7:24 PM, 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
>
> <tokLogo.png>
>
>
> tamar@tok-media.com
> Tel: +972 2 6409736
> Mob: +972 54 8356490
> Fax: +972 2 5612956
>
>
>
>
>
--
*Tamar Fraenkel *
Senior Software Engineer, TOK Media
[image: Inline image 1]
tamar@tok-media.com
Tel: +972 2 6409736
Mob: +972 54 8356490
Fax: +972 2 5612956
Re: TimeUUID
Posted by aaron morton <aa...@thelastpickle.com>.
not a great deal of difference, personally I would stick with seconds since epoch (it is probably slightly faster).
Cheers
-----------------
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 28/02/2012, at 7:24 PM, 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
>
> <tokLogo.png>
>
> tamar@tok-media.com
> Tel: +972 2 6409736
> Mob: +972 54 8356490
> Fax: +972 2 5612956
>
>
>
Re: TimeUUID
Posted by "R. Verlangen" <ro...@us2.nl>.
For querying purposes it would be better to use readable strings because
you can really get information out of that.
TimeUUID is just a unique value based on time; but not only the time.
2012/2/28 Tamar Fraenkel <ta...@tok-media.com>
> 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
>
> [image: Inline image 1]
>
> tamar@tok-media.com
> Tel: +972 2 6409736
> Mob: +972 54 8356490
> Fax: +972 2 5612956
>
>
>
>