There's no easy and efficient way to implement auto_increment keys in
cassandra. So people usually use UUIDs
(http://en.wikipedia.org/wiki/UUID) for this purpose, which is
considered globally unique.
If you can use one of the fields from your data model as a unique key,
better use it instead of ge
ourse, I'm assuming a single data center, here. Memcached isn't too
> useful for this if you need to update scores at two data centers.
>
> I'm not sure how much the 0.6 row cache might help in this case, too.
>
> - "Andriy Bohdan" wrote:
>
>> H
Hello guys
I have a pretty similar task. There's a need to store tags of products
with score. Score may go up and down and tags have to be ordered by
their score for each product. Score is updated "very" often.
I was thinking of using the following model (simplified here for clarity):
Product =
