Return-Path: 
 <user-return-19869-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 68A568611
	for <apmail-cassandra-user-archive@www.apache.org>;
 Tue, 16 Aug 2011 13:46:26 +0000 (UTC)
Received: (qmail 13120 invoked by uid 500); 16 Aug 2011 13:46:24 -0000
Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org
Received: (qmail 13054 invoked by uid 500); 16 Aug 2011 13:46:23 -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 13046 invoked by uid 99); 16 Aug 2011 13:46:23 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Aug 2011 13:46:23 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of watcherfr@gmail.com designates
 209.85.210.48 as permitted sender)
Received: from [209.85.210.48] (HELO mail-pz0-f48.google.com) (209.85.210.48)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Aug 2011 13:46:15 +0000
Received: by pzk34 with SMTP id 34so4446862pzk.21
        for <user@cassandra.apache.org>; Tue, 16 Aug 2011 06:45:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=ToQIhvseLLGTBssNKBCvIhsA00CU9VSp3Zv/ZeKG3tY=;
        b=pfjUiGrY+uJUaGFD5pIkzsLpz+RArpDgykRoVs3BB9nIfBCat9Ne32a3d3E9StPNJD
         bRzu/MRNQq/wlZ/sDb6IvP3jrPekCWZNmIiw08RmT9WfNxKrp9idtuY3H9YjaY0o6wkf
         n/cS7U/YWG+XtGQQ69lTIkSG79WXz65nwQemI=
MIME-Version: 1.0
Received: by 10.142.201.6 with SMTP id y6mr2474142wff.314.1313502354612; Tue,
 16 Aug 2011 06:45:54 -0700 (PDT)
Received: by 10.142.203.21 with HTTP; Tue, 16 Aug 2011 06:45:54 -0700 (PDT)
Date: Tue, 16 Aug 2011 15:45:54 +0200
Message-ID: 
 <CAHwsXYmTUR0JoceY-EfhNc8=He0cbN1w2QB4aGBLb6G71Ei2xw@mail.gmail.com>
Subject: Truncate column families
From: Philippe <watcherfr@gmail.com>
To: user <user@cassandra.apache.org>
Content-Type: multipart/alternative; boundary=000e0cd32be042225104aa9f99fa
X-Virus-Checked: Checked by ClamAV on apache.org

--000e0cd32be042225104aa9f99fa
Content-Type: text/plain; charset=ISO-8859-1

Hello, what are the guarantees regarding truncates issued through the CLI ?

I have a 3 node ring at RF=3. No writes going to the keyspace at issue here.
I go to the CLI on one of the nodes and issue a truncate on all CF of the
keyspace. I run a list [CF] and make sure there is no data.

When I run a repair on that node & keyspace, data appears back into the CFs.
Why is that ?

Thaks

--000e0cd32be042225104aa9f99fa
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hello, what are the guarantees regarding truncates issued through the CLI ?=
<div><br></div><div>I have a 3 node ring at RF=3D3. No writes going to the =
keyspace at issue here.</div><div>I go to the CLI on one of the nodes and i=
ssue a truncate on all CF of the keyspace. I run a list [CF] and make sure =
there is no data.</div>
<div><br></div><div>When I run a repair on that node &amp; keyspace, data a=
ppears back into the CFs. Why is that ?</div><div><br></div><div>Thaks</div=
>

--000e0cd32be042225104aa9f99fa--