f_v1, f_n2, f_v2, f_n3, f_v3)
>
> );
>
>
>
> And denormalize the data when you import to the table :
>
> One line in Oracle table with K filters become C(3, K) lines in C* table.
>
>
>
> Best regards,
>
> Minh
>
>
>
> *From:* Alaa Zubaidi (P
Porting an SQL data model to Cassandra is an anti-pattern - don't do it!
Instead, focus on developing a new data model that capitalizes on the key
strengths of Cassandra - distributed, scalable, fast writes, fast direct
access. Complex and ad-hoc queries are anti-patterns as well. I'll leave it
to
From: Alaa Zubaidi (PDF) [mailto:alaa.zuba...@pdf.com]
Sent: lundi 11 mai 2015 20:32
To: user@cassandra.apache.org
Subject: CQL Data Model question
Hi,
I am trying to port an Oracle Table to Cassandra.
the table is a wide table (931 columns) and could have millions of rows.
name, filter1, filter2
Hi,
I am trying to port an Oracle Table to Cassandra.
the table is a wide table (931 columns) and could have millions of rows.
name, filter1, filter2filter30, data1, data2...data900
The user would retrieve multiple rows from this table and filter (30 filter
columns) by one or more (up to 3)
