Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I was going through the documentation of CQLv3.0
Should we specify composite keys across updates and selects like ‘a:b:1’ incase my comparator or key_validation is ascii, ascii, int?
There is no mention on <select expression> in select or way to specify composite columns and rows in update too <primary/composite key name>
Expecting some help over it
CQL 3 takes care of managing the actual composite types and values for you. CQL 3 rows are not necessarily the same as the underlying Cassandra rows (“storage engine rows”). The composite values are abstracted into separate columns.
The example at http://www.datastax.com/dev/blog/schema-in-cassandra-1-1 may help in understanding the transformation.