You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benedict (JIRA)" <ji...@apache.org> on 2018/09/13 16:24:02 UTC
[jira] [Commented] (CASSANDRA-14749) Collection Deletions for
Dropped Columns in 2.1/3.0 mixed-mode can delete rows
[ https://issues.apache.org/jira/browse/CASSANDRA-14749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16613722#comment-16613722 ]
Benedict commented on CASSANDRA-14749:
--------------------------------------
[3.0|https://github.com/belliottsmith/cassandra/tree/14749] [CI|https://circleci.com/workflow-run/c877e18e-ea8e-45ec-b090-4652445f487d]
Since this has already been reviewed in CASSANDRA-14568, if either of you could give a quick cursory +1 to the split, that would be great. I felt it warranted its own CHANGES.txt entry and JIRA.
> 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: Core
> Reporter: Benedict
> Assignee: Benedict
> Priority: Major
> 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.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org