Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 12034 invoked from network); 24 Mar 2010 17:55:45 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 24 Mar 2010 17:55:45 -0000 Received: (qmail 72764 invoked by uid 500); 24 Mar 2010 17:55:45 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 72752 invoked by uid 500); 24 Mar 2010 17:55:45 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 72744 invoked by uid 99); 24 Mar 2010 17:55:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Mar 2010 17:55:45 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of rantav@gmail.com designates 209.85.216.202 as permitted sender) Received: from [209.85.216.202] (HELO mail-px0-f202.google.com) (209.85.216.202) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Mar 2010 17:55:36 +0000 Received: by pxi40 with SMTP id 40so26042pxi.9 for ; Wed, 24 Mar 2010 10:55:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=C/N9FmShQ3Iky63rRJR/B/1NNDFCO7ZZVcxmE2WWIcI=; b=HeNbw2KUsyjZSoNMO0kKLjm56FU4k+9zDSTW5a0dtrCrTzA9E9a4tVr/mvvZybNps0 Fe8N3y+6JYMK/jTWEZbffFp9Yg2i3UMxLvijpRq1/dQIx7R7Cfz/1kUFDVuCLyD5EQGK NsRyniYG5Ued3EQLzkihm1dTwenSHXol9cWrc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=bVe1B5kUB+JXPGn3GbqS3A30T5HSnkc2/9GNwEcwUZDzrlkl/8ktxCNsNAC59J9UYr ccRHWPiqq4fyU+mbtnsu9EXMEOM1ojuTj2IFKiujoU2TaBn0TZ1rzmRGtu9GsFjibPjT 17bkkdQY/nO5N45342odWS1gdlY8wziI9nj1k= MIME-Version: 1.0 Received: by 10.143.87.3 with SMTP id p3mr2579900wfl.53.1269453314688; Wed, 24 Mar 2010 10:55:14 -0700 (PDT) In-Reply-To: References: Date: Wed, 24 Mar 2010 19:55:14 +0200 Message-ID: Subject: Re: how to delete data From: Ran Tavory To: Jonathan Ellis Cc: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=000e0cd4cd96e18a0f04828fa1ff X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd4cd96e18a0f04828fa1ff Content-Type: text/plain; charset=UTF-8 I'm willing to give it a try. Where do I start, except for applying the patch in the bug? On Wed, Mar 24, 2010 at 2:30 PM, Jonathan Ellis wrote: > Currently there is no good way to do this. We're planning to add > "truncate" support in > https://issues.apache.org/jira/browse/CASSANDRA-531, let me know if > you want to work on that. :) > > -Jonathan > > On Wed, Mar 24, 2010 at 4:03 AM, Ran Tavory wrote: > > What's the recommended way to delete data? > > For example, I want to wipe out an entire column family data from disk > with > > minimal effort. > > I could: > > > > stop all hosts in the cluster > > restart them until they finish playing commit logs > > stop them again > > delete all CF related files in my data directory at every node > > start cluster again > > ... but this is tedious. is there a nicer way? > > > --000e0cd4cd96e18a0f04828fa1ff Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I'm willing to give it a try.=C2=A0
Where do I sta= rt, except for applying the patch in the bug?

On Wed, Mar 24, 2010 at 2:30 PM, Jonathan Ellis <= jbellis@gmail.com> wrote= :
Currently there is no good way to do this. = =C2=A0We're planning to add
"truncate" support in
https://issues.apache.org/jira/browse/CASSANDRA-531, let me know= if
you want to work on that. :)

-Jonathan

On Wed, Mar 24, 2010 at 4:03 AM, Ran Tavory <rantav@gmail.com> wrote:
> What's the recommended way to delete data?
> For example, I want to wipe out an entire column family data from disk= with
> minimal effort.
> I could:
>
> stop all hosts in the cluster
> restart them until they finish playing commit logs
> stop them again
> delete all CF related files in my data directory at every node
> start cluster again
> ... but this is tedious. is there a nicer way?
>

--000e0cd4cd96e18a0f04828fa1ff--