[mailto:doanduy...@gmail.com]
Sent: vendredi 2 mai 2014 12:29
To: user@cassandra.apache.org
Subject: Re: *Union* data type modeling in Cassandra
Hello Ngoc Minh
I'd go with the first data model. To solve the null <-> tombstone issue, just
do not insert them at runtime if value is null
Hello Ngoc Minh
I'd go with the first data model. To solve the null <-> tombstone issue,
just do not insert them at runtime if value is null.
If only numvalue double != null -> INSERT INTO data_table(key,numvalue)
VALUES(...,...);
If only numvalues list != null -> INSERT INTO
data_table(key,nu
Hello all,
I don't know whether it is the right place to discuss about data modeling with
Cassandra.
We would like to have your feedbacks/recommendations on our schema modeling:
1. Our data are stored in a CF by their unique key (K)
2. Data type could be one of the following: Doubl
