incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen Connolly <stephen.alan.conno...@gmail.com>
Subject Re: row keys
Date Sat, 05 Feb 2011 21:37:53 GMT
you really need to know how you will be pulling the data back out again. you
could use the object id as the row key, timestamp as the column name and
long/lat as the value... that would allow you to query by object is and get
the time sorted location trace... but if you have a lot of frequent readings
for each object, that would be a poor model because very large rows can
impact performance... in that case you might use the object id combined with
the timestamp rounded to the nearest hour (say) to keep the row size
lower...

but if you are more interested in tracking multiple objects per time, you
might use the timestamp as row key, object id as column name, etc...

with cassandra you need to know what queries you will want to make and
design for that

- Stephen

---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 5 Feb 2011 18:17, "Sean Ochoa" <sean.m.ochoa@gmail.com> wrote:

Mime
View raw message