cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-12705) Add column definition kind to system schema dropped columns
Date Mon, 26 Sep 2016 01:44:20 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-12705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15521768#comment-15521768
] 

Stefania commented on CASSANDRA-12705:
--------------------------------------

An initial commit is available [here|https://github.com/stef1927/cassandra/commits/12705],
based on the patch for CASSANDRA-12582. The commit adds the column definition kind to {{SchemaKeyspace.DroppedColumns}},
the handling of the schema migration during upgrade is missing.

> 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: Distributed Metadata
>            Reporter: Stefania
>             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
(v6.3.4#6332)

Mime
View raw message