You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2019/07/09 16:20:00 UTC
[jira] [Updated] (CASSANDRA-15204) Toughen up column drop/recreate
validations in 3.0/3.11
[ https://issues.apache.org/jira/browse/CASSANDRA-15204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Yeschenko updated CASSANDRA-15204:
------------------------------------------
Severity: Normal
Complexity: Normal
Discovered By: Code Inspection
Bug Category: Parent values: Correctness(12982)Level 1 values: Persistent Corruption / Loss(12986)
Reviewers: Sam Tunnicliffe
Status: Open (was: Triage Needed)
> 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
>
> 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org