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 2018/11/26 18:16:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16699387#comment-16699387 ]
Aleksey Yeschenko commented on CASSANDRA-14913:
-----------------------------------------------
[Code|https://github.com/iamaleksey/cassandra/commits/14913], [CI|https://circleci.com/workflow-run/f88826a9-62c0-42bb-84ec-7e403ef80747].
> 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: Distributed Metadata
> Reporter: Aleksey Yeschenko
> Assignee: Aleksey Yeschenko
> Priority: Major
> Fix For: 4.0.x
>
>
> 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