Stefano Ortolani created CASSANDRA-13573: --------------------------------------------
Summary: sstabledump doesn't print out tombstone information for frozen set collection Key: CASSANDRA-13573 URL: https://issues.apache.org/jira/browse/CASSANDRA-13573 Project: Cassandra Issue Type: Bug Components: Tools Reporter: Stefano Ortolani Schema and data" {noformat} CREATE TABLE ks.cf ( hash blob, report_id timeuuid, subject_ids frozen<set<int>>, PRIMARY KEY (hash, report_id) ) WITH CLUSTERING ORDER BY (report_id DESC); INSERT INTO ks.cf (hash, report_id, subject_ids) VALUES (0x1213, now(), {1,2,4,5}); {noformat} sstabledump output is: {noformat} sstabledump mc-1-big-Data.db [ { "partition" : { "key" : [ "1213" ], "position" : 0 }, "rows" : [ { "type" : "row", "position" : 16, "clustering" : [ "ec01eed0-49d9-11e7-b39a-97a96f529c02" ], "liveness_info" : { "tstamp" : "2017-06-05T10:29:57.434856Z" }, "cells" : [ { "name" : "subject_ids", "value" : "" } ] } ] } ] {noformat} While the values are really there: {noformat} cqlsh:ks> select * from cf ; hash | report_id | subject_ids --------+--------------------------------------+------------- 0x1213 | 02bafff0-49d9-11e7-b39a-97a96f529c02 | {1, 2, 4} {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org