You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Vincent White (JIRA)" <ji...@apache.org> on 2019/01/03 07:28:00 UTC
[jira] [Created] (CASSANDRA-14948) Backport dropped column checks
to 3.11
Vincent White created CASSANDRA-14948:
-----------------------------------------
Summary: Backport dropped column checks to 3.11
Key: CASSANDRA-14948
URL: https://issues.apache.org/jira/browse/CASSANDRA-14948
Project: Cassandra
Issue Type: Bug
Reporter: Vincent White
Assignee: Vincent White
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.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org