[ https://issues.apache.org/jira/browse/CASSANDRA-15204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Yeschenko updated CASSANDRA-15204: ------------------------------------------ Fix Version/s: (was: 3.11.x) (was: 3.0.x) 3.11.5 3.0.19 Source Control Link: [855fc91596b10a89a504b3491952d06ffe93618d|https://github.com/apache/cassandra/commit/855fc91596b10a89a504b3491952d06ffe93618d] Since Version: 3.0.0 Status: Resolved (was: Ready to Commit) Resolution: Fixed Cheers, committed as [855fc91596b10a89a504b3491952d06ffe93618d|https://github.com/apache/cassandra/commit/855fc91596b10a89a504b3491952d06ffe93618d] to 3.0 and merged into 3.11. > 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.19, 3.11.5 > > > 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