Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of shahab.yunus@gmail.com
 designates 209.85.214.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAEDUwd1ZMOr1siVZuHguDLNoS468V-w_YdcFD9Di3cPMXGm6Vw@mail.gmail.com>
References: 
 <CAGW2whRwKJGo7qnTF00OWb_2NU5Uaf95eXTbyj2gHMabuoOboQ@mail.gmail.com>
	<CAEDUwd1ZMOr1siVZuHguDLNoS468V-w_YdcFD9Di3cPMXGm6Vw@mail.gmail.com>
Date: Wed, 9 Oct 2013 14:56:17 -0400
Message-ID: 
 <CAEo-6+Q63sr26nghSWdKWQmd=+KCg1M+KL51uYTcs64OJAmOeg@mail.gmail.com>
Subject: Re: Deleting data using timestamp
From: Shahab Yunus <shahab.yunus@gmail.com>
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Content-Type: multipart/alternative; boundary=bcaec5430d4eb8041d04e853709e

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

Ahh, yes, 'compaction'. I blanked out while mentioning repair and cleanup.
That is in fact what needs to be done first and what I meant. Thanks
Robert.

Regards,
Shahab


On Wed, Oct 9, 2013 at 1:50 PM, Robert Coli <rcoli@eventbrite.com> wrote:

> On Wed, Oct 9, 2013 at 7:35 AM, Ravikumar Govindarajan <
> ravikumar.govindarajan@gmail.com> wrote:
>
>> What is the quick way to delete old-data and at the same time make sure
>> read [doesn't] churn through all deleted columns?
>>
>
> Use a database that isn't log structured?
>
> But seriously, in 2.0 there's this :
>
> https://issues.apache.org/jira/browse/CASSANDRA-5514
>
> Which allows for timestamp hints at query time.
>
> And...
>
> https://issues.apache.org/jira/browse/CASSANDRA-5228
>
> Which does compaction expiration of entire SSTables based on TTL.
>
> =Rob
>
>

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

<div dir=3D"ltr">Ahh, yes, &#39;compaction&#39;. I blanked out while mentio=
ning repair and cleanup. That is in fact what needs to be done first and wh=
at I meant. Thanks Robert.=A0<div><br></div><div>Regards,</div><div>Shahab<=
/div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Wed,=
 Oct 9, 2013 at 1:50 PM, Robert Coli <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:rcoli@eventbrite.com" target=3D"_blank">rcoli@eventbrite.com</a>&gt;</spa=
n> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">On Wed, Oct 9, 2013 at 7:35=
 AM, Ravikumar Govindarajan <span dir=3D"ltr">&lt;<a href=3D"mailto:ravikum=
ar.govindarajan@gmail.com" target=3D"_blank">ravikumar.govindarajan@gmail.c=
om</a>&gt;</span> wrote:<br>
<div class=3D"gmail_extra">
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204=
);border-left-style:solid;padding-left:1ex"><div dir=3D"ltr"><div>What is t=
he quick way to delete old-data and at the same time make sure read [doesn&=
#39;t] churn through all deleted columns?</div>

</div></blockquote><div><br></div><div>Use a database that isn&#39;t log st=
ructured?</div><div><br></div><div>But seriously, in 2.0 there&#39;s this :=
</div><div><br></div><div><a href=3D"https://issues.apache.org/jira/browse/=
CASSANDRA-5514" target=3D"_blank">https://issues.apache.org/jira/browse/CAS=
SANDRA-5514</a></div>

<div><br></div><div>Which allows for timestamp hints at query time.</div><d=
iv><br></div><div>And...</div><div>=A0<br></div><div><a href=3D"https://iss=
ues.apache.org/jira/browse/CASSANDRA-5228" target=3D"_blank">https://issues=
.apache.org/jira/browse/CASSANDRA-5228</a><br>

</div><div><br></div><div>Which does compaction expiration of entire SSTabl=
es based on TTL.</div><div><br></div><div>=3DRob</div><div><br></div></div>=
</div></div>
</blockquote></div><br></div>

--bcaec5430d4eb8041d04e853709e--