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

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 2.1.3
• Severity: Low
• Impacts: Clients
• Assignee: Tom Hobbs
• Reporter: Oded Peer

Authors

Tom Hobbs

Reviewers

Aleksey Yeschenko

• Created: 11/Sep/14 08:10
• Updated: 06/Nov/19 21:57
• Resolved: 02/Jan/15 18:01

Description

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

Issue Links

• is duplicated by: CASSANDRA-8353 Prepared statement doesn't revalidate after table schema changes
• is superceded by: CASSANDRA-10786 Include hash of result set metadata in prepared statement id
• relates to: CASSANDRA-7566 DROP TABLE should also drop prepared statements associated to