[
https://issues.apache.org/jira/browse/CASSANDRA-11655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Lohfink reassigned CASSANDRA-11655:
-----------------------------------------
Assignee: Chris Lohfink
> sstabledump doesn't print out tombstone information for deleted collection
> column
> ---------------------------------------------------------------------------------
>
> Key: CASSANDRA-11655
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11655
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Reporter: Wei Deng
> Assignee: Chris Lohfink
> Labels: Tools
>
> Pretty trivial to reproduce.
> {noformat}
> 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
> {noformat}
> Now if you run sstabledump (even after taking the
> [patch|https://github.com/yukim/cassandra/tree/11654-3.0] for
> CASSANDRA-11654) against the newly generated SSTable like the following:
> {noformat}
> ~/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" }
> ]
> }
> ]
> }
> ]
> {noformat}
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
