[
https://issues.apache.org/jira/browse/CASSANDRA-14846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16971160#comment-16971160
]
Alex Petrov commented on CASSANDRA-14846:
-----------------------------------------
Probably the best and most intuitive for schema changes to work is to treat any
added column as a completely new column (which is also likely to be a
prerequisite for implementing better/consistent schema). However, adding
something like undrop sounds like a good thing for quick recovery in case of
accidental removal.
> Drop/Add Column Pre-existing Data Inconsistency
> -----------------------------------------------
>
> Key: CASSANDRA-14846
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14846
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Semantics, Local/SSTable
> Reporter: Benedict Elliott Smith
> Priority: Normal
>
> If we drop a column, any data that is compacted before we add a column with
> the same name (and compatible type) will be lost, but any data that was not
> compacted will continue to be returned. This seems problematic - surely we
> should consider all data prior to a Drop to be lost? Re-adding a column of
> the same name should reset the column’s contents?
> This would also permit us to not worry about the types being consistent in
> the case of a dropped column (only alter column need worry about this)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
