[
https://issues.apache.org/jira/browse/CASSANDRA-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14706404#comment-14706404
]
Sylvain Lebresne commented on CASSANDRA-7910:
---------------------------------------------
bq. What is the workaround?
Don't use a wildcard, list the columns your care about in the statement. I
think it's good practice anyway.
> 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
> Labels: client-impacting
> 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)
