"Does my above table falls under the category of wide rows in Cassandra or not?" --> It depends on the cardinality. For each distinct test_id, how many combinations of client_name/record_data do you have ?
By the way, why do you put the record_data as part of primary key ? In your table partiton key = test_id, client_name = first clustering column, record_data = second clustering column On Fri, Sep 19, 2014 at 5:41 PM, Check Peck <comptechge...@gmail.com> wrote: > I am trying to use wide rows concept in my data modelling design for > Cassandra. We are using Cassandra 2.0.6. > > CREATE TABLE test_data ( > test_id int, > client_name text, > record_data text, > creation_date timestamp, > last_modified_date timestamp, > PRIMARY KEY (test_id, client_name, record_data) > ) > > So I came up with above table design. Does my above table falls under the > category of wide rows in Cassandra or not? > > And is there any problem If I have three columns in my PRIMARY KEY? I > guess PARTITION KEY will be test_id right? And what about other two? > > In this table, we can have multiple record_data for same client_name. > > Query Pattern will be - > > select client_name, record_data from test_data where test_id = 1; >
