[CASSANDRA-11655] sstabledump doesn't print out tombstone information for deleted collection column

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0.6, 3.6
• Component/s: Legacy/Tools
• Labels: Tools
• Severity: Normal
• Since Version: 3.0.4
• Assignee: Chris Lohfink
• Reporter: Wei Deng

Authors

Chris Lohfink

Reviewers

Yuki Morishita

• Created: 26/Apr/16 04:52
• Updated: 16/Apr/19 09:30
• Resolved: 29/Apr/16 19:34

Description

Pretty trivial to reproduce.

echo "CREATE KEYSPACE IF NOT EXISTS testks WITH replication = {'class': 'SimpleStrategy', 'replication_factor': '1'};" | cqlsh
echo "CREATE TABLE IF NOT EXISTS testks.testcf ( k int, c text, val0_int int, val1_set_of_int set<int>, PRIMARY KEY (k, c) );" | cqlsh
echo "INSERT INTO testks.testcf (k, c, val0_int, val1_set_of_int) VALUES (1, 'c1', 100, {1, 2, 3, 4, 5});" | cqlsh
echo "delete val1_set_of_int from testks.testcf where k=1 and c='c1';" | cqlsh
echo "select * from testks.testcf;" | cqlsh
nodetool flush testks testcf

Now if you run sstabledump (even after taking the patch for CASSANDRA-11654) against the newly generated SSTable like the following:

~/cassandra-trunk/tools/bin/sstabledump ma-1-big-Data.db
[
  {
    "partition" : {
      "key" : [ "1" ],
      "position" : 0
    },
    "rows" : [
      {
        "type" : "row",
        "position" : 18,
        "clustering" : [ "c1" ],
        "liveness_info" : { "tstamp" : 1461645231352208 },
        "cells" : [
          { "name" : "val0_int", "value" : "100" }
        ]
      }
    ]
  }
]

You will see that the collection-level Deletion Info is nowhere to be found, so you will not be able to know "markedForDeleteAt" or "localDeletionTime" for this collection tombstone.

Issue Links

• relates to: CASSANDRA-11656 sstabledump has inconsistency in deletion_time printout