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

Aleksey Yeschenko commented on CASSANDRA-15204:
-----------------------------------------------

bq. Is this the right time to backport CASSANDRA-14913? (you mentioned on that 
ticket that you planned to do it at some point).

Perhaps, as follow up. Will address the nit on commit, thanks.

> Toughen up column drop/recreate validations in 3.0/3.11
> -------------------------------------------------------
>
>                 Key: CASSANDRA-15204
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15204
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Cluster/Schema
>            Reporter: Aleksey Yeschenko
>            Assignee: Aleksey Yeschenko
>            Priority: Normal
>             Fix For: 3.0.x, 3.11.x
>
>
> After CASSANDRA-8099 it’s no longer possible to safely drop/add columns with 
> incompatible types. In 4.0 we validate this correctly, but in 3.0 we don’t,
> and that can result in unreadable sstables (corrupted serialization headers 
> causing simple columns to be read as complex or vice versa).
> This patch brings 3.0 in line with 4.0 restrictions, making such corruption 
> impossible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to