Benedict created CASSANDRA-14846:
------------------------------------
Summary: Drop/Add Column Pre-existing Data Inconsistency
Key: CASSANDRA-14846
URL: https://issues.apache.org/jira/browse/CASSANDRA-14846
Project: Cassandra
Issue Type: Bug
Reporter: Benedict
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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
