[ https://issues.apache.org/jira/browse/CASSANDRA-14749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16613795#comment-16613795 ]
Benedict commented on CASSANDRA-14749: -------------------------------------- Good job I did (split this out) - this time, Aleksey pointed out the {{getDroppedColumn}} invokes another method {{getDroppedColumn(name, isStatic)}} with a default parameter of {{false}} for {{isStatic}} I've pushed an update, but I think the defaulting variant of {{getDroppedColumn}} probably shouldn't exist. > 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org