Return-Path: 
 <user-return-42232-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org>
X-Original-To: apmail-cassandra-user-archive@www.apache.org
Delivered-To: apmail-cassandra-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 1F9E1C6B7
	for <apmail-cassandra-user-archive@www.apache.org>;
 Thu,  7 Aug 2014 15:34:07 +0000 (UTC)
Received: (qmail 71706 invoked by uid 500); 7 Aug 2014 15:34:04 -0000
Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org
Received: (qmail 71663 invoked by uid 500); 7 Aug 2014 15:34:04 -0000
Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@cassandra.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@cassandra.apache.org>
List-Post: <mailto:user@cassandra.apache.org>
List-Id: <user.cassandra.apache.org>
Reply-To: user@cassandra.apache.org
Delivered-To: mailing list user@cassandra.apache.org
Received: (qmail 71651 invoked by uid 99); 7 Aug 2014 15:34:04 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Aug 2014 15:34:04 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of doanduyhai@gmail.com designates
 209.85.214.172 as permitted sender)
Received: from [209.85.214.172] (HELO mail-ob0-f172.google.com)
 (209.85.214.172)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Aug 2014 15:34:01 +0000
Received: by mail-ob0-f172.google.com with SMTP id wn1so3045153obc.17
        for <user@cassandra.apache.org>; Thu, 07 Aug 2014 08:33:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=EZ2wg1vaiwFOiL9NqAUxScVVLPupnYyAC6NDSYKjv4I=;
        b=GNZcpbzOtpU0M13l6YG2PoThgAS8La9n9qH3gzxWAfChPU5h/8IVcRAHLwtAAHynKo
         dHvhul9fru7QqrI3kg2xhPJWcFK3ZrMMn831kWi0+CKhOuvDCPaiR7FA6NfEMRTnDx9f
         3QhRN+hamINrDiJk4taFWeKDiQLN6s1l+rQqLxUGsDYc42EQy6bSc5wHbUu5hWxoqwm4
         T+5dS7JclzwwhpGOqLbf2H+AgtH1xHtZaxkJrkQ/R3R5zrXUnLWUN3klz+EkDtII/qRi
         saBA5YXytsu8WbxlwKjp/hHhL/2/qbqVbZxvB1sDVqje8rDmt2Tv6RYrx3/IZXRU9pEu
         nFVA==
MIME-Version: 1.0
X-Received: by 10.60.145.239 with SMTP id sx15mr23985501oeb.72.1407425616442;
 Thu, 07 Aug 2014 08:33:36 -0700 (PDT)
Received: by 10.76.28.72 with HTTP; Thu, 7 Aug 2014 08:33:36 -0700 (PDT)
Date: Thu, 7 Aug 2014 17:33:36 +0200
Message-ID: 
 <CABNXB2D7vhrskb3Fr=_YZ85MHLL-_9aM3UPkuPOkZoFJQa7uMw@mail.gmail.com>
Subject: Delete By Partition Key Implementation
From: DuyHai Doan <doanduyhai@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=047d7b5d474eea782305000bcfa1
X-Virus-Checked: Checked by ClamAV on apache.org

--047d7b5d474eea782305000bcfa1
Content-Type: text/plain; charset=UTF-8

Hello all

 Usually, when using DELETE in CQL3 on some fields, C* creates tombstone
columns for those fields.

 Now if I delete a whole PARTITION (delete from MyTable where
partitionKey=...), what will C* do ? Will it create as many tombstones as
there are physical columns on this partition or will it just mark this
partition as "deleted" (Row Key deletion marker) ?

 On a side note, if I insert a bunch of physical columns in one partition
with the SAME ttl value, after a while they will appear as expired, would
C* need to scan the whole partition on disk to see which columns to expire
or could it see that the whole partition is indeed expired thanks to meta
data/ Partition key cache kept in memory ?  I was thinking about the
estimate histograms for TTL but I don't know in detail how it work

 Regards

 Duy Hai  DOAN

--047d7b5d474eea782305000bcfa1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello all<div><br></div><div>=C2=A0Usually, when using DEL=
ETE in CQL3 on some fields, C* creates tombstone columns for those fields.<=
/div><div><br></div><div>=C2=A0Now if I delete a whole PARTITION (delete fr=
om MyTable where partitionKey=3D...), what will C* do ? Will it create as m=
any tombstones as there are physical columns on this partition or will it j=
ust mark this partition as &quot;deleted&quot; (Row Key deletion marker) ?<=
/div>
<div><br></div><div>=C2=A0On a side note, if I insert a bunch of physical c=
olumns in one partition with the SAME ttl value, after a while they will ap=
pear as expired, would C* need to scan the whole partition on disk to see w=
hich columns to expire or could it see that the whole partition is indeed e=
xpired thanks to meta data/ Partition key cache kept in memory ? =C2=A0I wa=
s thinking about the estimate histograms for TTL but I don&#39;t know in de=
tail how it work</div>
<div><br></div><div>=C2=A0Regards</div><div><br></div><div>=C2=A0Duy Hai =
=C2=A0DOAN</div><div><br></div></div>

--047d7b5d474eea782305000bcfa1--