Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-11930

Range tombstone serialisation between 2.1 and 3.0 nodes (in 3.0 -> 2.1 direction) is broken for some Thrift deletions

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Fix Version/s: 3.0.7, 3.7
    • Component/s: Legacy/Coordination
    • Labels:
      None
    • Severity:
      Normal

      Description

      LegacyLayout.LegacyRangeTombstoneList::serialize() has a broken assumption that a range tombstone implies CompositeType. This is incorrect, as you can have non-CompositeType range tombstones created via Thrift in 2.1, and as such wrapping clusteringComparator.subtypes() in a CompositeType is incorrect. On 2.1/2.2 side, when decoding the range tombstone list, RangeTombstoneList::deserialize() will use the raw type to decode start and end bounds, which will end up being confused by the extra 2 bytes in the beginning (short length) plus end of component header in the end.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                thobbs Tyler Hobbs
                Reporter:
                iamaleksey Aleksey Yeschenko
                Authors:
                Tyler Hobbs
                Reviewers:
                Aleksey Yeschenko
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: