You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "C. Scott Andreas (JIRA)" <ji...@apache.org> on 2018/11/16 04:11:00 UTC

[jira] [Updated] (CASSANDRA-14846) Drop/Add Column Pre-existing Data Inconsistency

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

C. Scott Andreas updated CASSANDRA-14846:
-----------------------------------------
    Component/s: Local Write-Read Paths

> 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: Local Write-Read Paths
>            Reporter: Benedict
>            Priority: Major
>
> 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
(v7.6.3#76005)

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