Hi Jon,
Thanks for your guidance.
In above mentioned table i can have different scale depending on Report.
One report may have 1 rows.
Second report may have half million rows.
Third report may have 1 million rows.
Fourth report may have 10 million rows.
As this is timeseries data that was
How much data do you plan to store in each table?
I’ll be honest, this doesn’t sound like a Cassandra use case at first glance.
1 table per report x 1000 is going to be a bad time. Odds are with different
queries, you’ll need multiple views, so lets call that a handful of tables per
report.
Looking for cassandra expert's recommendation on above usecase, please
reply.
On Mon, Apr 17, 2017 at 7:37 PM, Naresh Yadav wrote:
> Hi all,
>
> This is my existing table configured on apache-cassandra-3.0.9:
>
> CREATE TABLE report_id1 (
>mc_id text,
>tag_id text,
>e_date timestamp.
Hi all,
This is my existing table configured on apache-cassandra-3.0.9:
CREATE TABLE report_id1 (
mc_id text,
tag_id text,
e_date timestamp.
value text
PRIMARY KEY ((mc_id, tag_id), e_date)
}
I create table dynamically for each report from application. Need to
support upto 1000 re
