[
https://issues.apache.org/jira/browse/CASSANDRA-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13239534#comment-13239534
]
Tyler Hobbs commented on CASSANDRA-4084:
----------------------------------------
I'm suggesting that we need to support column value validators based on only
one or more components of the composite name rather than all of the components.
In the example I gave, there will be many different values of <user_id>, but
if the last component is "birthdate", you always want to validate that the
column value is an integer.
This did seem like something that would be important for CQL, but I couldn't
find another ticket covering this, and it seemed like something that might be
missed.
> 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
