[
https://issues.apache.org/jira/browse/CASSANDRA-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13239557#comment-13239557
]
Sylvain Lebresne commented on CASSANDRA-4084:
---------------------------------------------
So, in CQL3 you can declare:
{noformat}
CREATE TABLE someTable (
row_key int,
user_id uuid,
name text,
age int
PRIMARY KEY(row_key, user_id)
)
{noformat}
This will be stored exactly as in your example. In other words, a given user
will be internally stored as 2 columns:
{noformat}
row key | column name | column value
--------|---------------------------|-------------
42 | ab332-daf2-00133-331:name | tom
42 | ab332-daf2-00133-331:age | 33
{noformat}
> Better validator support for composite comparator CFs
> -----------------------------------------------------
>
> Key: CASSANDRA-4084
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4084
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Tyler Hobbs
> Priority: Minor
>
> Perhaps this should be part of replacing super columns with composites, but
> we essentially need something analogous to sub-column validators for when
> composites are used in a way that's similar to super columns (multiple fields
> for each "super column" in a row). As an example use case, suppose you have
> a wide row holding users where the comparator is (<user_id>, <field>), and
> <field> might be either "name" or "age"; ideally, you can validate "name" as
> UT8Type and "age" as IntegerType.
> Allowing wildcards to be used for components in the column name portion of
> the ColumnDef might be a reasonable approach.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
