You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Tyler Hobbs (JIRA)" <ji...@apache.org> on 2015/01/01 00:14:14 UTC

[jira] [Updated] (CASSANDRA-7910) wildcard prepared statements are incorrect after a column is added to the table

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

Tyler Hobbs updated CASSANDRA-7910:
-----------------------------------
    Attachment: 7910-trunk.txt
                7910-2.1.txt

The attached patches invalidate any prepared statements that deal with the affected table whenever columns are added, dropped, or altered.  The 2.1 patch also backports a minor refactor of IMigrationListener from trunk.

I've pushed a [dtest branch|https://github.com/thobbs/cassandra-dtest/tree/CASSANDRA-7910] as well.

> wildcard prepared statements are incorrect after a column is added to the table
> -------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-7910
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7910
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Oded Peer
>            Assignee: Tyler Hobbs
>            Priority: Minor
>             Fix For: 2.1.3
>
>         Attachments: 7910-2.1.txt, 7910-trunk.txt, PreparedStatementAfterAddColumnTest.java
>
>
> 1. Prepare a statement with a wildcard in the select clause.
> 2. Alter the table - add a column
> 3. execute the prepared statement
> Expected result - get all the columns including the new column
> Actual result - get the columns except the new column
> Attached a test using cassandra-unit



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