[CASSANDRA-16712] DROP COMPACT STORAGE does not invalidate prepared statements as it should - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Bug
Status: Resolved
Priority: Normal
Resolution: Fixed
Fix Version/s: 3.0.25, 3.11.11
Component/s: Cluster/Schema
Labels:
None

Bug Category:
Correctness - Transient Incorrect Response
Severity:
Normal
Complexity:
Normal
Discovered By:
Unit Test
Platform:

All
Impacts:

None
Since Version:

3.0.0
Source Control Link:

https://github.com/apache/cassandra/commit/0e1f217079fa01366d9c8d758498016300467d31
Test and Documentation Plan:

Hide

One of the result expected by a test was wrong. The test was modified to expect the correct behavior.

Show
One of the result expected by a test was wrong. The test was modified to expect the correct behavior.

Description

DROP COMPACT STORAGE might change the number of columns of a table but as the prepared statement cache is not invalidate the query will not return the correct set of columns until the statement as been invalidate. That can lead to a surprising behavior where the resultset change at un expected point in time.

This problem only affect 3.0 and 3.11

Attachments

Issue Links

is related to

CASSANDRA-16671 Cassandra can return no row when the row columns have been deleted.

Resolved

relates to

CASSANDRA-16361 DROP COMPACT STORAGE should invalidate prepared statements still using CompactTableMetadata

Resolved

Activity

People

Assignee:: Benjamin Lerer

Reporter:: Benjamin Lerer

Authors:: Benjamin Lerer

Reviewers:: Benjamin Lerer, Michael Semb Wever

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 04/Jun/21 09:00

Updated:: 04/Jun/21 16:00

Resolved:: 04/Jun/21 11:29

Time Tracking

Estimated:

Not Specified

Remaining:

Logged:

50m