[ https://issues.apache.org/jira/browse/CASSANDRA-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15026957#comment-15026957 ]
Tyler Hobbs commented on CASSANDRA-7910: ---------------------------------------- Hmm, that's a good point. Perhaps we should include a hash of the result set metadata (in some way) in the prepared statement ID? > 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 > 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)