You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Michael Semb Wever (Jira)" <ji...@apache.org> on 2020/12/18 09:34:01 UTC
[jira] [Commented] (CASSANDRA-16361) DROP COMPACT STORAGE should
invalidate prepared statements still using CompactTableMetadata
[ https://issues.apache.org/jira/browse/CASSANDRA-16361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17251628#comment-17251628 ]
Michael Semb Wever commented on CASSANDRA-16361:
------------------------------------------------
+1
> DROP COMPACT STORAGE should invalidate prepared statements still using CompactTableMetadata
> -------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-16361
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16361
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/CQL
> Reporter: Caleb Rackliffe
> Assignee: Caleb Rackliffe
> Priority: Normal
> Fix For: 4.0-beta
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When we drop compact storage from a table, existing prepared statements continue to refer to an instance of {{CompactTableMetadata}}, rather than being invalidated so they can be assigned a new {{TableMetadata}} instance. There are perhaps some brute force ways to fix this, like bouncing the node, but that obviously sub-optimal.
> One idea is to have {{TableMetadata#changeAffectsPreparedStatements()}} return true when we go from having to not having the DENSE flag. It should be pretty easy to validate a fix with a small addition to {{CompactTableTest}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org