Hi Cass,
just a hint from the off - if I got it right you have:
Table 1: PRIMARY KEY ( (event_day,event_hr),event_time)
Table 2: PRIMARY KEY (event_day,event_time)
Assuming your events to write come in by wall clock time, the first
table design will have a hotspot on a specific node getting al
, velocity and variety. It doesn’t look like
your data has the volume or velocity that a standard RDBMS cannot handle.
Mohammed
From: Kai Wang [mailto:dep...@gmail.com]
Sent: Thursday, February 19, 2015 6:06 AM
To: user@cassandra.apache.org
Subject: Re: Data tiered compaction and data model question
Any feedback on data tiered compaction? Have anybody used it?
On Thu, Feb 19, 2015 at 6:06 AM, Kai Wang wrote:
> What's the typical size of the data field? Unless it's very large, I don't
> think table 2 is a "very" wide row (10x20x60x24=288000 events/partition at
> worst). Plus you only need to
What's the typical size of the data field? Unless it's very large, I don't
think table 2 is a "very" wide row (10x20x60x24=288000 events/partition at
worst). Plus you only need to store 30 days of data. The over data size is
288000x30=8,640,000 events. I am not even sure if you need C* depending on
10-20 per minute is the average. Worstcase can be 10x of avg.
On Wed, Feb 18, 2015 at 4:49 PM, Mohammed Guller
wrote:
> What is the maximum number of events that you expect in a day? What is
> the worst-case scenario?
>
>
>
> Mohammed
>
>
>
> *From:* cass savy [mailto:casss...@gmail.com]
> *Sen
What is the maximum number of events that you expect in a day? What is the
worst-case scenario?
Mohammed
From: cass savy [mailto:casss...@gmail.com]
Sent: Wednesday, February 18, 2015 4:21 PM
To: user@cassandra.apache.org
Subject: Data tiered compaction and data model question
We want to track
