a.apache.org>"
mailto:user@cassandra.apache.org>>
Date: Tuesday, February 12, 2013 2:56 PM
To: user mailto:user@cassandra.apache.org>>
Subject: Re: Seeking suggestions for a use case
Would you mind sharing your schema on the list? It would be useful to see how
you modeled yo
Would you mind sharing your schema on the list? It would be useful to see
how you modeled your data. Or you could email me privately if you want.
Thanks
Boris
On Tue, Feb 12, 2013 at 4:11 PM, Hiller, Dean wrote:
> Yes, the limit of the width of a row is approximately in the millions,
> perhaps
"user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Date: Tuesday, February 12, 2013 1:08 PM
To: user mailto:user@cassandra.apache.org>>
Subject: Re: Seeking suggestions for a use case
Thanks. So in your use case, you actually keep part
We are using cassandra for time series as well with PlayOrm. A guess is
we will be doing equal reads and writes on all the data going back 10
years(currently in production we are write heavy right now). We have
60,000 virtual tables (one table per sensor we read from and yes we have
that many sen
Your use case is 100% on the money for Cassandra. But let me take a
chance to slam the other NoSQLs. (not really slam but you know)
Riak is a key-value store. It is not a column family store where a
rowkey has a map of sorted values. This makes the time series more
awkward as the time series has t
