[jira] [Commented] (CASSANDRA-16712) DROP COMPACT STORAGE does not invalidate prepared statements as it should
[ https://issues.apache.org/jira/browse/CASSANDRA-16712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17357239#comment-17357239 ] Michael Semb Wever commented on CASSANDRA-16712: +1 CASSANDRA-16361 missed including this change on the 3.0 and 3.11 branches. > 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.x, 3.11.x > > 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16712) DROP COMPACT STORAGE does not invalidate prepared statements as it should
[ https://issues.apache.org/jira/browse/CASSANDRA-16712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17357203#comment-17357203 ] Benjamin Lerer commented on CASSANDRA-16712: || Branches || CI || | [3.0|https://github.com/apache/cassandra/pull/1039] | [j8|https://app.circleci.com/pipelines/github/blerer/cassandra/132/workflows/ab9add3f-4f8a-4993-946d-3ad7a59b4a66] | | [3.0|https://github.com/apache/cassandra/pull/1040] | [j8|https://app.circleci.com/pipelines/github/blerer/cassandra/131/workflows/150a3108-3afb-4a73-a70e-cd79b78ffd6e] | > 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.x, 3.11.x > > 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org