cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stu Hood (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (CASSANDRA-891) Add ValidateWith to CF definitions
Date Thu, 26 Aug 2010 19:51:54 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Stu Hood reopened CASSANDRA-891:
--------------------------------


Needs a default value for default_validation_class in order to handle users upgrading from
beta1 to beta2. See CASSANDRA-1437 for a full explanation of the issue, but in summary, something
like:
{{union { null, string } default_validation_class = null;}}
...should mean the CfMetaData.inflate will see a null on default_validation_class, rather
than the schema failure caused by r989344.

> Add ValidateWith to CF definitions
> ----------------------------------
>
>                 Key: CASSANDRA-891
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-891
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Jon Hermes
>            Priority: Minor
>             Fix For: 0.7 beta 2
>
>         Attachments: 891-rebased.txt, 891.txt
>
>
> VW would take an AbstractType like CompareWith and validate the data on insert.  Should
default to BytesType (i.e. no-op).
> This would have the side effect of giving the CLI enough information about values to
parse and display them intelligently rather than just hex byte values.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message