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
ohammed
>>>
>>>
>>>
>>> *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
>>>
>>>
>>&
t 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:* Dat
avy [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 events in log Cf/table and should be able to query for
> events that occurred in r
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
We want to track events in log Cf/table and should be able to query for
events that occurred in range of mins or hours for given day. Multiple
events can occur in a given minute. Listed 2 table designs and leaning
towards table 1 to avoid large wide row. Please advice on
*Table 1*: not very wid
