This may sound silly as there are no null values in SQL's composite primary key. But just want to confirm if we can have the same in CQL3?
So, we have a table like this to store wide rows:
CREATE TABLE keyspace12.colFamily1
(
id text,
colname text,
colvalue blob,
PRIMARY KEY (id,colname, colvalue)
) WITH COMPACT STORAGE
And we have some cases where colname is null. Can I do that? If yes, then how? If NO, then what are the ways to store wide columns rows where we can have some null in first part of composite column of cassandra(As per Thrift's convention)?
The related questions are: CQL3 and millions of columns composite key use case and Cassandra -How to create composite column name (not key) using cqlsh