Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of rcoli@eventbrite.com
 designates 209.85.128.43 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAPmnz8EpjC0DUdGrv5zKtp=AKvf1khw5U8cibGxhwKDqEKk4hw@mail.gmail.com>
References: <CDCA6DAD.29848%Dean.Hiller@nrel.gov>
	<CDCA6EF2.29851%Dean.Hiller@nrel.gov>
	<CAPmnz8EpjC0DUdGrv5zKtp=AKvf1khw5U8cibGxhwKDqEKk4hw@mail.gmail.com>
Date: Tue, 28 May 2013 16:26:04 -0700
Message-ID: 
 <CAEDUwd1Ltacwm29+KW+BJNZb6Jx+nHXymnrVOhUsadZ6Mxg-2A@mail.gmail.com>
Subject: Re: data clean up problem
From: Robert Coli <rcoli@eventbrite.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Tue, May 28, 2013 at 2:38 PM, Bryan Talbot <btalbot@aeriagames.com> wrote:
> I think what you're asking for (efficient removal of TTL'd write-once data)
> is already in the works but not until 2.0 it seems.

If your entire dataset in a keyspace or column family is deleted every
[small time period], then maybe use TRUNCATE?

Two caveats :

1) https://issues.apache.org/jira/browse/CASSANDRA-4655 - TRUNCATE
will leave undelivered hints untouched until 1.2.6
2) TRUNCATE will create a snapshot unless you (unsafely!!!!!!!
danger!!!!!!!!) disable this feature [1]

Alternately, perhaps a datastore with immutable data files is not for you? :D

=Rob
[1] https://issues.apache.org/jira/browse/CASSANDRA-3710