[ 
https://issues.apache.org/jira/browse/CASSANDRA-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902513#action_12902513
 ] 

Jon Hermes edited comment on CASSANDRA-891 at 8/25/10 12:49 PM:
----------------------------------------------------------------

Sorry, the change is in the getValueValidator method at the bottom of 
CFMetaData which ThriftValidation calls.
It used to say "get my cfmd, get my cmd, get my validator", now it says, "get 
my cmfd, get my cmd, if cmd.validator then use it, else cmfd.validator, else 
BytesType".

      was (Author: jhermes):
    Sorry, the change is in the getValidator method at the bottom of CFMetaData 
which ThriftValidation calls.
It used to say "get my cfmd, get my cmd, get my validator", now it says, "get 
my cmfd, get my cmd, if cmd.validator then use it, else cmfd.validator, else 
BytesType".
  
> 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.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.

Reply via email to