You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2014/09/16 19:43:34 UTC

[jira] [Updated] (CASSANDRA-7833) Collection types validation is incomplete

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

Sylvain Lebresne updated CASSANDRA-7833:
----------------------------------------
    Attachment: 7833.txt

Attaching trivial fix. It's on the 2.0. The 2.1 branch actually has (commented out) tests for this (in CollectionsTest.testInvalidCollectionsMix) but as it's not in 2.0, I'll just activate the tests while merging.

> Collection types validation is incomplete
> -----------------------------------------
>
>                 Key: CASSANDRA-7833
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7833
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>             Fix For: 2.0.11
>
>         Attachments: 7833.txt
>
>
> The collection types will complain if a value has less values than advertised, or if some of those values don't validate, but it does check that there is no remaining bytes after the collection. One consequence is that if you prepare {{INSERT INTO t(k, s) VALUES (0, ?)}} where {{s}} is a set, and you pass a map value (with the same type for keys and values than the set), then no error will be issued.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)