ani [mailto:98kerm...@gmail.com]
> *Envoyé :* lundi 30 mai 2016 13:42
> *À :* user@cassandra.apache.org
> *Objet :* Cassandra data modeling for a social network
>
>
>
> We are using Cassandra for our social network and we are designing/data
> modeling tables we need, it is c
ani [mailto:98kerm...@gmail.com]
Envoyé : lundi 30 mai 2016 13:42
À : user@cassandra.apache.org
Objet : Cassandra data modeling for a social network
We are using Cassandra for our social network and we are designing/data
modeling tables we need, it is confusing for us and we don't know how to desi
We are using Cassandra for our social network and we are designing/data
modeling tables we need, it is confusing for us and we don't know how to
design some tables and we have some little problems!
*As we understood for every query we have to have different tables*, and
for example user A is follo
If you are collecting time series data, and assuming the flying turtles we live
on that swim through time do not stop, you will want to partition your data.
(background http://www.slideshare.net/mattdennis/cassandra-data-modeling)
Lets say it makes sense for you to partition by month (may not
: M Vieira
To: user@cassandra.apache.org
Sent: Thursday, 29 September 2011 2:54 PM
Subject: Cassandra data modeling
I'm trying to get my head around Cassandra data modeling, but I can't quite see
what would be the best approach to the problem I have.
The supposed scenario:
You have around
I'm trying to get my head around Cassandra data modeling, but I can't quite
see what would be the best approach to the problem I have.
The supposed scenario:
You have around 100 domains, each domain have from few hundreds to millions
of possible URLs (think of different combinations o
