You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Sam Tunnicliffe (JIRA)" <ji...@apache.org> on 2015/12/04 21:34:11 UTC

[jira] [Updated] (CASSANDRA-8146) Fix validation of collections in TriggerExecutor

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

Sam Tunnicliffe updated CASSANDRA-8146:
---------------------------------------
    Component/s: Coordination

> Fix validation of collections in TriggerExecutor
> ------------------------------------------------
>
>                 Key: CASSANDRA-8146
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8146
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Coordination
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>             Fix For: 2.1.1
>
>         Attachments: 8146.txt
>
>
> TriggerExecutor.validate uses o.a.c.cql.QueryProcessor (i.e. the cql2 version) to validate cells in generated mutations. This suffers from the same issue with collections as described in CASSANDRA-7665.
> With cql2 being removed in 3.0, TriggerExecutor in trunk does the right thing and uses the Cell's validateFields method, so we should just do the same thing in 2.1.



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