You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Josh McKenzie (Jira)" <ji...@apache.org> on 2020/04/18 19:55:00 UTC

[jira] [Updated] (CASSANDRA-12705) Add column definition kind to system schema dropped columns

     [ https://issues.apache.org/jira/browse/CASSANDRA-12705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh McKenzie updated CASSANDRA-12705:
--------------------------------------
    Bug Category: Parent values: Availability(12983)Level 1 values: Unavailable(12994)

> Add column definition kind to system schema dropped columns
> -----------------------------------------------------------
>
>                 Key: CASSANDRA-12705
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12705
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Legacy/Distributed Metadata
>            Reporter: Stefania Alborghetti
>            Assignee: Stefania Alborghetti
>            Priority: Normal
>             Fix For: 4.0
>
>
> Both regular and static columns can currently be dropped by users, but this information is currently not stored in {{SchemaKeyspace.DroppedColumns}}. As a consequence, {{CFMetadata.getDroppedColumnDefinition}} returns a regular column and this has caused problems such as CASSANDRA-12582.
> We should add the column kind to {{SchemaKeyspace.DroppedColumns}} so that {{CFMetadata.getDroppedColumnDefinition}} can create the correct column definition. However, altering schema tables would cause inter-node communication failures during a rolling upgrade, see CASSANDRA-12236. Therefore we should wait for a full schema migration when upgrading to the next major version.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org