[
https://issues.apache.org/jira/browse/CASSANDRA-12705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15529160#comment-15529160
]
Aleksey Yeschenko commented on CASSANDRA-12705:
-----------------------------------------------
For major upgrades we don't really care. Nodes with different messaging
versions don't exchange schema between each other, in either direction. So
unlike the cdc mess we had to live through (minor upgrade), here, all is 'easy'.
This will change *after* 4.0 though, with new schema protocols. Not going to
affect this ticket.
> 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)
