[
https://issues.apache.org/jira/browse/CASSANDRA-16361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-16361:
-------------------------------------------
Fix Version/s: (was: 4.0-beta)
4.0-beta4
Since Version: 4.0-alpha1
Source Control Link:
https://github.com/apache/cassandra/commit/d9859d231f24781b7ebf4dd93bb4584fb4bc7538
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Cleaned up some trailing whitespace, and added the CHANGES.txt entry.
Committed as
[d9859d231f24781b7ebf4dd93bb4584fb4bc7538|https://github.com/apache/cassandra/commit/d9859d231f24781b7ebf4dd93bb4584fb4bc7538].
> 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-beta4
>
> Time Spent: 40m
> 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: [email protected]
For additional commands, e-mail: [email protected]
