s to come
> up with a data model that avoids the strangulation. CQL is a nice
> syntactic layer, but, at the end of the day, to avoid performance
> black holes, you have to understand how the data is going to be
> stored by Cassandra in rows and columns.
> >
>
e day,
> to avoid performance black holes, you have to understand how the data is
> going to be stored by Cassandra in rows and columns.
> >
> >
> > -Original Message-
> > From: Simon Chemouil [mailto:schemo...@gmail.com]
> > Sent: Monday, June 02, 2014 10:
understand how the data is going to be
> stored by Cassandra in rows and columns.
>
>
> -Original Message-
> From: Simon Chemouil [mailto:schemo...@gmail.com]
> Sent: Monday, June 02, 2014 10:56 AM
> To: user@cassandra.apache.org
> Subject: Re: Performance migrati
lto:schemo...@gmail.com]
Sent: Monday, June 02, 2014 10:56 AM
To: user@cassandra.apache.org
Subject: Re: Performance migrating from MySQL to C*
Hi Moshe,
Thanks for your answer and the link on time series.
We'd like to query on more than one dataName, but also on the time range and on
an arbi
((dataName, dayRange, discriminator), time,
> sensorId)
>
> );
>
>
>
>
>
> Hope this helps.
>
>
>
> *From:*Simon Chemouil [mailto:schemo...@gmail.com]
> *Sent:* Wednesday, May 28, 2014 6:26 PM
> *To:* user@cassandra.apache.org
> *Subject:* P
Hello DuyHai,
Thanks for your answer. Unfortunately having one 'metricType' field or
storing each metric in different partitions is roughly the same for us
if we have to "merge" them on the timestamp client-side. Your solution
can reduce the number of queries which is practical but we might get
qu
DOUBLE,
PRIMARY KEY ((dataName, dayRange, discriminator), time, sensorId)
);
Hope this helps.
From: Simon Chemouil [mailto:schemo...@gmail.com]
Sent: Wednesday, May 28, 2014 6:26 PM
To: user@cassandra.apache.org
Subject: Performance migrating from MySQL to C*
Hi,
First, sorry for the
Hello Simon
There is definitely some data modeling issue there.
Your first data model was quite good, except the usage of
map. Collections in C* are not meant to be used to store lots
of values because they are loaded entirely in memory server side every time
you access them. An alternative for
Hi,
First, sorry for the length of this mail. TL;DR: DataModeling timeseries
with an extra dimension, and C* not handling stress well; MySQL doesn't
scale as well but handles the queries way better on similar hardware.
==
Context:
We've been evaluating Cassandra for a while now (~1 m
