ette.ch
>Data: 25/12/2011 10.19
>A:
>Ogg: Re: Counters and Top 10
>
>With Composite Column Name, you can even have column composed of sore
>(int) and userid (uuid or whatever). Empty column value to avoid
>repeating user UUID.
>
>
>2011/12/22 R. Verlangen :
&
With Composite Column Name, you can even have column composed of sore
(int) and userid (uuid or whatever). Empty column value to avoid
repeating user UUID.
2011/12/22 R. Verlangen :
> I would suggest you to create a CF with a single row (or multiple for
> historical data) with a date as key (utf8
In our case we didn't need an exact daily top-10 list of pages, just a good
guess of it. So the way we did it was to insert a column with a short TTL
(e.g. 12 hours) with the page id as the column name. Then, when constructing
the top-10 list, we'd just slice through the entire list of unexpi
Counters only update the value of the column, they cannot be used as column
names. So you cannot have a dynamically updating top ten list using counters.
You have a couple of options. First use something like redis if that fits your
use case. Redis could either be the database of record for the
I would suggest you to create a CF with a single row (or multiple for
historical data) with a date as key (utf8, e.g. 2011-12-22) and multiple
columns for every user's score. The column (utf8) would then be the score +
something unique of the user (e.g. hex representation of the TimeUUID). The
valu