[
https://issues.apache.org/jira/browse/CASSANDRA-16712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-16712:
---------------------------------------
Fix Version/s: (was: 3.11.x)
(was: 3.0.x)
3.11.11
3.0.25
Since Version: 3.0.0
Source Control Link:
https://github.com/apache/cassandra/commit/0e1f217079fa01366d9c8d758498016300467d31
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Patch committed into 3.0 at 0e1f217079fa01366d9c8d758498016300467d31 and merged
into cassandra-3.11
> DROP COMPACT STORAGE does not invalidate prepared statements as it should
> --------------------------------------------------------------------------
>
> Key: CASSANDRA-16712
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16712
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Schema
> Reporter: Benjamin Lerer
> Assignee: Benjamin Lerer
> Priority: Normal
> Fix For: 3.0.25, 3.11.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{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
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
