cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sébastien Pierre <sebastien.pie...@gmail.com>
Subject Re: Cassandra to store logs as a list
Date Wed, 20 Jan 2010 22:08:51 GMT
Ahhh, OK !

I got a little bit confused in the terminology, but your explanation really
made it clear, thanks a lot ! I don't think there will be more than a
million columns per row, as it's already aggregated by campaign and day.

I'll let you know how this works for me :)

 -- Sébastien


2010/1/20 Brandon Williams <driftx@gmail.com>

> 2010/1/20 Sébastien Pierre <sebastien.pierre@gmail.com>
>
>> Hmmm, but the only thing that is not clear is how I would store a lot of
>> values for the same key ? With redis, I was using keys like
>> "campaign:<campaign_id>:<YYYY><MM><DD>" to store a *list*
of
>> JSON-serialized log info, and the list could scale to litteraly millions of
>> entries. From my understanding, Cassandra can only store 1 value per (colum
>> key, field) couple, doesn't it ?
>
>
> Each row in Cassandra can have an arbitrary number of columns consisting of
> a name and value (and timestamp.)  The columns are sorted on the name based
> on the type used, which is why I recommended the TimeUUIDType so you would
> get time-based sorting.
>
> So your row keys would be like "campaign:<campaign_id>:<YYYY><MM><DD>",
> your column names a TimeUUIDType, and your values the JSON data.
>
> Millions of columns in a row is ok, I would begin using caution beyond
> perhaps 100M though.
>
> -Brandon
>

Mime
View raw message