Thanks Ngoc, Jack
On Tue, May 12, 2015 at 4:56 AM, Ngoc Minh VO
wrote:
> Hello,
>
>
>
> The problem with your approach is: you will need to specify all the 30
> filters (in the pre-defined order in PK) when querying.
>
>
>
> I would go for this data model:
>
> CREATE TABLE t (
>
> name text
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
Hello,
The problem with your approach is: you will need to specify all the 30 filters
(in the pre-defined order in PK) when querying.
I would go for this data model:
CREATE TABLE t (
name text,
filter_name1 text, filter_value1 text,
filter_name2 text, filter_value2 text,
filter_n
