You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benedict (JIRA)" <ji...@apache.org> on 2019/01/03 11:26:00 UTC
[jira] [Updated] (CASSANDRA-14913) Forbid re-adding static columns
as regular and vice versa
[ https://issues.apache.org/jira/browse/CASSANDRA-14913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benedict updated CASSANDRA-14913:
---------------------------------
Component/s: (was: Legacy/Distributed Metadata)
Cluster/Schema
> Forbid re-adding static columns as regular and vice versa
> ---------------------------------------------------------
>
> Key: CASSANDRA-14913
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14913
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Schema
> Reporter: Aleksey Yeschenko
> Assignee: Aleksey Yeschenko
> Priority: Major
> Fix For: 4.0
>
>
> Re-adding a dropped column with an incompatible kind (dropped regular re-added as static, or dropped static re-added as regular) can ultimately result in corruption (see CASSANDRA-14843 for more context). In 3.x, unfortunately, we don’t persist enough context when dropping a column. In trunk, however, we do, and it’s trivial to forbid this operation, as we should.
--
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