Yes. TimedUUIDs use 60bits for time with 100 nanosecond precision, but in
addition they have other parts to prevent collision. Assuming that everyone
plays fair (i.e. you are not actively trying to create collisions), you are by
orders of magnitudes more likely to be hit by a meteorite than having two keys
colliding with each other.
-Ville
On Jan 20, 2010, at 23:03, Sébastien Pierre wrote:
> Hi Brandon,
>
> And would TimeUUIDType allow nanosecond-level precision ? There's going to be
> a lot of data logged, and I would like to avoid having events being erased.
>
> -- Sébasiten
>
> 2010/1/20 Brandon Williams <dri...@gmail.com>
> 2010/1/20 Sébastien Pierre <sebastien.pie...@gmail.com>
>
> Hi there !
>
> I only looked briefly at Cassandra, and I would like to know how good it
> would be at storing logs. I've been using Redis and its LIST structure to
> store JSON-encoded log info, in the following fashion:
>
> redis["site:0"] = ["{'visitor':1,'referer':'http://...'}",
> "{'visitor':1,'referer':'http://...'}]
>
> The problem is that the volume of logs is quite big, and would quickly
> exhaust the memory on the server and kill performance -- which is why I'm
> looking at Cassandra. Hence this question:
> would it be possible to store multiple (ordered) values for the same key in
> Cassandra ?
>
> You could handle this equivalently in Cassandra by making the row name
> 'site:0', using a TimeUUIDType for the column, and JSON serialized data as
> the value.
>
> -Brandon
>
