cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7910) wildcard prepared statements are incorrect after a column is added to the table
Date Fri, 12 Sep 2014 16:47:34 GMT

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

Aleksey Yeschenko commented on CASSANDRA-7910:
----------------------------------------------

Cannot just sneakily change the number of columns returned, because of Skip_metadata flag
in native proto v3, for one.

Agree with Yuki here. This would be the right thing to do (maybe not on *any* table change
- we don't care about options stuff being changed).

> 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
>         Attachments: 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)

Mime
View raw message