cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1814) validation is inefficient
Date Sat, 11 Dec 2010 07:37:16 GMT

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

Hudson commented on CASSANDRA-1814:
-----------------------------------

Integrated in Cassandra-0.7 #70 (See [https://hudson.apache.org/hudson/job/Cassandra-0.7/70/])
    

> validation is inefficient
> -------------------------
>
>                 Key: CASSANDRA-1814
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1814
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.7.0 rc 1
>            Reporter: Gary Dusbabek
>            Assignee: Gary Dusbabek
>            Priority: Minor
>             Fix For: 0.7.0
>
>         Attachments: v3-0001-type-validations-that-generate-less-garbage.txt
>
>
> We do all validation by simply calling AbstractType.getString().  This generates garbage
needlessly and has a lot of overhead.
> A simpler interface would be to make AbstractType.validate abstract and have the child
classes implement it in an intelligent and efficient way.
> EDIT: Somewhat related:  It looks like we're attempting to validate column names in ThriftValidation.validateColumns().
 Is this intentional?  Nevermind that part. I get it.

-- 
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