[ https://issues.apache.org/jira/browse/CASSANDRA-11932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tyler Hobbs updated CASSANDRA-11932: ------------------------------------ Summary: Range tombstones generated instead of regular ones between 2.1 and 3.0 nodes (in 3.0 -> 2.1 direction) for some tables (was: Range tombstones generated instead of regular once between 2.1 and 3.0 nodes (in 3.0 -> 2.1 direction) for some tables) > Range tombstones generated instead of regular ones between 2.1 and 3.0 nodes > (in 3.0 -> 2.1 direction) for some tables > ---------------------------------------------------------------------------------------------------------------------- > > Key: CASSANDRA-11932 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11932 > Project: Cassandra > Issue Type: Bug > Components: Coordination > Reporter: Aleksey Yeschenko > Assignee: Tyler Hobbs > Fix For: 3.0.x, 3.x > > > Mixed and dynamic Thrift CFs deletions of the dynamic component are being > translated into range tombstones in 3.0 -> 2.1 direction. On 3.0 side they > are whole row deletions, and {{LegacyLayout::fromRow(CFMetaData, Row)}} turns > them into range tombstones even for non-composite, dynamic and mixed Thrift > CFs. They should be converted into single-cell deletions instead. > This is not a correctness problem, strictly speaking, and on its own 'only' > causes digest mismatches on reads (and thus a lot of extra traffic w/ CL > > ONE) and less efficient representation on wire, though breaks some upgrades > in combination with CASSANDRA-11930. > To reproduce, create a mixed CF while both nodes are on 2.1, upgrade one node > to 3.0, and with cqlsh connected to 3.0 remove some rows. Then do a {{SELECT > *}} query in cqlsh when connected to 2.1. -- This message was sent by Atlassian JIRA (v6.3.4#6332)