[
https://issues.apache.org/jira/browse/CASSANDRA-14749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
C. Scott Andreas updated CASSANDRA-14749:
-----------------------------------------
Severity: Critical (was: Normal)
Complexity: Challenging
Discovered By: Adhoc Test
Bug Category: Parent values: Correctness(12982)Level 1 values: Persistent
Corruption / Loss(12986)
Since Version: 3.0.0
> Collection Deletions for Dropped Columns in 2.1/3.0 mixed-mode can delete rows
> ------------------------------------------------------------------------------
>
> Key: CASSANDRA-14749
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14749
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Core
> Reporter: Benedict
> Assignee: Benedict
> Priority: Urgent
> Fix For: 3.0.18
>
>
> Similar to CASSANDRA-14568, if a 2.1 node sends a response to a 3.0 node
> containing a deletion for a dropped collection column, instead of deleting
> the collection, we will delete the row containing the collection.
>
> This is an admittedly unlikely cluster state but, during such a state, a
> great deal of data loss could happen.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
