[ 
https://issues.apache.org/jira/browse/CASSANDRA-18760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17755857#comment-17755857
 ] 

Stefan Miklosovic commented on CASSANDRA-18760:
-----------------------------------------------

[j17 
5.0|https://app.circleci.com/pipelines/github/instaclustr/cassandra/2949/workflows/095d5680-1669-464b-a840-f06ffa9cb4c4]
[j11 
4.1|https://app.circleci.com/pipelines/github/instaclustr/cassandra/2943/workflows/88e6fc40-8a6f-4664-8a92-37e2b75938fa]
[j11 
4.0|https://app.circleci.com/pipelines/github/instaclustr/cassandra/2944/workflows/c3fb38b7-ed56-45a8-aa5c-84635edd872e]
[j8 
3.11|https://app.circleci.com/pipelines/github/instaclustr/cassandra/2945/workflows/85b5a07c-e751-44f1-be31-dcced62f38fd]
[j8 
3.0|https://app.circleci.com/pipelines/github/instaclustr/cassandra/2946/workflows/2e3f7452-b121-4166-b7f8-48b4d380656b]

5.0 flakiness is CASSANDRA-18360


> 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]

Reply via email to