[ 
https://issues.apache.org/jira/browse/CASSANDRA-14948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Yeschenko updated CASSANDRA-14948:
------------------------------------------
    Component/s: Cluster/Schema

> Backport dropped column checks to 3.0 and 3.11
> ----------------------------------------------
>
>                 Key: CASSANDRA-14948
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14948
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Cluster/Schema
>            Reporter: Vincent White
>            Assignee: Vincent White
>            Priority: Low
>             Fix For: 3.0.19, 3.11.5
>
>
> This is a follow on from CASSANDRA-14913 and CASSANDRA-14843 that introduced 
> some fixes to prevent and mitigate data corruption caused by dropping a 
> column then re-adding it with the same name but an incompatible type (e.g. 
> simple int to a complex map<>) or different kind (regular/static). 
> This patch backports the checks that now exist in trunk. This does include 
> adding a column to the dropped_columns table to keep track of static columns 
> like trunk, not sure it we are able to make that change in 3.11.x. 
> Also not sure what our stance on backporting just the isValueCompatibleWith 
> check to 3.0 is. I'd be for it since it prevents recreating a simple column 
> as a map (or vice-versa) which will basically always lead to corruption.
> ||C* 3.11.x||
> |[Patch|https://github.com/vincewhite/cassandra/commit/3986b53b8acaf1d3691f9b35fd098a40667c520f]|



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to