[
https://issues.apache.org/jira/browse/CASSANDRA-18760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-18760:
------------------------------------------
Status: Ready to Commit (was: Review In Progress)
> Need to block the ability to DROP table column of 'map' type and add back as
> 'blob' type
> ----------------------------------------------------------------------------------------
>
> Key: CASSANDRA-18760
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18760
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Schema
> Reporter: Paul Ayers
> Assignee: Stefan Miklosovic
> Priority: Urgent
> Labels: 4.0.10
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.0.x, 5.x
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Recently hit an un-recoverable situation in Cassandra 4.0.10 after dropping a
> 'map' column and adding it back as a 'blob', which caused corruption that
> neither offline nor online scrub could fix.
> When dropping a 'blob' column and attempting to add it back as a 'map' type,
> the operation is blocked with:
> {code:java}
> InvalidRequest: Error from server: code=2200 [Invalid query] message="Cannot
> re-add previously dropped column 'col1' of type map<int, tinyint>,
> incompatible with previous type blob"
> {code}
> We need to do the same going from 'map' to 'blob' to avoid this potentially
> very bad scenario that can cause data loss.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
