Return-Path: 
 <commits-return-168172-apmail-cassandra-commits-archive=cassandra.apache.org@cassandra.apache.org>
X-Original-To: apmail-cassandra-commits-archive@www.apache.org
Delivered-To: apmail-cassandra-commits-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 862A4195F6
	for <apmail-cassandra-commits-archive@www.apache.org>;
 Fri, 29 Apr 2016 01:37:13 +0000 (UTC)
Received: (qmail 65506 invoked by uid 500); 29 Apr 2016 01:37:13 -0000
Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org
Received: (qmail 65473 invoked by uid 500); 29 Apr 2016 01:37:13 -0000
Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:commits-help@cassandra.apache.org>
List-Unsubscribe: <mailto:commits-unsubscribe@cassandra.apache.org>
List-Post: <mailto:commits@cassandra.apache.org>
List-Id: <commits.cassandra.apache.org>
Reply-To: dev@cassandra.apache.org
Delivered-To: mailing list commits@cassandra.apache.org
Received: (qmail 65378 invoked by uid 99); 29 Apr 2016 01:37:13 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Apr 2016 01:37:13 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 274A82C1F6C
	for <commits@cassandra.apache.org>; Fri, 29 Apr 2016 01:37:13 +0000 (UTC)
Date: Fri, 29 Apr 2016 01:37:13 +0000 (UTC)
From: "Chris Lohfink (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12962482.1461646332000.66217.1461893833158@Atlassian.JIRA>
In-Reply-To: <JIRA.12962482.1461646332000@Atlassian.JIRA>
References: <JIRA.12962482.1461646332000@Atlassian.JIRA>
 <JIRA.12962482.1461646332121@arcas>
Subject: [jira] [Updated] (CASSANDRA-11655) sstabledump doesn't print out
 tombstone information for deleted collection column
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


     [ https://issues.apache.org/jira/browse/CASSANDRA-11655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Lohfink updated CASSANDRA-11655:
--------------------------------------
    Attachment: trunk-11655v3.patch

> 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
>         Attachments: CASSANDRA-11655.patch, trunk-11655v2.patch, trunk-11655v3.patch
>
>
> 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)