Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 46339 invoked from network); 8 Feb 2011 15:19:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 8 Feb 2011 15:19:10 -0000 Received: (qmail 12259 invoked by uid 500); 8 Feb 2011 15:19:08 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 12234 invoked by uid 500); 8 Feb 2011 15:19:04 -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 12213 invoked by uid 99); 8 Feb 2011 15:19:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Feb 2011 15:19:04 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.210.172] (HELO mail-iy0-f172.google.com) (209.85.210.172) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Feb 2011 15:18:55 +0000 Received: by iym1 with SMTP id 1so5814261iym.31 for ; Tue, 08 Feb 2011 07:18:34 -0800 (PST) MIME-Version: 1.0 Received: by 10.231.205.205 with SMTP id fr13mr18840364ibb.120.1297178313538; Tue, 08 Feb 2011 07:18:33 -0800 (PST) Received: by 10.231.15.72 with HTTP; Tue, 8 Feb 2011 07:18:33 -0800 (PST) X-Originating-IP: [80.179.102.198] In-Reply-To: References: Date: Tue, 8 Feb 2011 17:18:33 +0200 Message-ID: Subject: Re: time to live rows From: David Boxenhorn To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=90e6ba4fc4b696bd67049bc6dc92 X-Virus-Checked: Checked by ClamAV on apache.org --90e6ba4fc4b696bd67049bc6dc92 Content-Type: text/plain; charset=ISO-8859-1 I hope you don't consider this a hijack of the thread... What I'd like to know is the following: The GC removes TTL rows some time after they expire, at its convenience. But will they stop being returned as soon as they expire? (This is the expected behavior...) On Tue, Feb 8, 2011 at 5:11 PM, Kallin Nagelberg wrote: > So the empty row will be ultimately removed then? Is there a way to > for the GC to verify this? > > Thanks, > -Kal > > On Tue, Feb 8, 2011 at 2:21 AM, Stu Hood wrote: > > The expired columns were converted into tombstones, which will live for > the > > GC timeout. The "empty" row will be cleaned up when those tombstones are > > removed. > > Returning the empty row is unfortunate... we'd love to find a more > > appropriate solution that might not involve endless scanning. > > See > > http://wiki.apache.org/cassandra/FAQ#i_deleted_what_gives > > http://wiki.apache.org/cassandra/FAQ#range_ghosts > > > > On Mon, Feb 7, 2011 at 1:49 PM, Kallin Nagelberg > > wrote: > >> > >> I also tried forcing a major compaction on the column family using JMX > >> but the row remains. > >> > >> On Mon, Feb 7, 2011 at 4:43 PM, Kallin Nagelberg > >> wrote: > >> > I tried that but I still see the row coming back on a list > >> > in the CLI. My concern is that there will be a pointer > >> > to an empty row for all eternity. > >> > > >> > -Kal > >> > > >> > On Mon, Feb 7, 2011 at 4:38 PM, Aaron Morton > > >> > wrote: > >> >> Deleting all the columns in a row via TTL has the same affect as > >> >> deleting th > >> >> row, the data will physically by removed during compaction. > >> >> > >> >> Aaron > >> >> > >> >> > >> >> On 08 Feb, 2011,at 10:24 AM, Bill Speirs > wrote: > >> >> > >> >> I don't think this is supported (but I could be completely wrong). > >> >> However, I'd love to see this functionality as well. > >> >> > >> >> How would one go about requesting such a feature? > >> >> > >> >> Bill- > >> >> > >> >> On Mon, Feb 7, 2011 at 4:15 PM, Kallin Nagelberg > >> >> wrote: > >> >>> Hey, > >> >>> > >> >>> I have read about the new TTL columns in Cassandra 0.7. In my case > I'd > >> >>> like to expire an entire row automatically after a certain amount of > >> >>> time. Is this possible as well? > >> >>> > >> >>> Thanks, > >> >>> -Kal > >> >>> > >> >> > >> > > > > > > --90e6ba4fc4b696bd67049bc6dc92 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I hope you don't consider this a hijack of the thread.= ..

What I'd like to know is the following:

The GC removes= TTL rows some time after they expire, at its convenience. But will they st= op being returned as soon as they expire? (This is the expected behavior...= )

On Tue, Feb 8, 2011 at 5:11 PM, Kallin Nagel= berg <ka= llin.nagelberg@gmail.com> wrote:
So the empty row will be ultimately removed then? Is there a way to
for the GC to verify this?

Thanks,
-Kal

On Tue, Feb 8, 2011 at 2:21 AM, Stu Hood <stuhood@gmail.com> wrote:
> The expired columns were converted into tombstones, which will live fo= r the
> GC timeout. The "empty" row will be cleaned up when those to= mbstones are
> removed.
> Returning the empty row is unfortunate... we'd love to find a more=
> appropriate solution that might not involve endless scanning.
> See
> http://wiki.apache.org/cassandra/FAQ#i_deleted_what_gives=
> http://wiki.apache.org/cassandra/FAQ#range_ghosts
>
> On Mon, Feb 7, 2011 at 1:49 PM, Kallin Nagelberg
> <kallin.nagelberg@gma= il.com> wrote:
>>
>> I also tried forcing a major compaction on the column family using= JMX
>> but the row remains.
>>
>> On Mon, Feb 7, 2011 at 4:43 PM, Kallin Nagelberg
>> <kallin.nagelberg= @gmail.com> wrote:
>> > I tried that but I still see the row coming back on a list >> > <columnfamily> in the CLI. My concern is that there wil= l be a pointer
>> > to an empty row for all eternity.
>> >
>> > -Kal
>> >
>> > On Mon, Feb 7, 2011 at 4:38 PM, Aaron Morton <aaron@thelastpickle.com>
>> > wrote:
>> >> Deleting all the columns in a row via TTL has the same af= fect as
>> >> deleting th
>> >> row, the data will physically by removed during compactio= n.
>> >>
>> >> Aaron
>> >>
>> >>
>> >> On 08 Feb, 2011,at 10:24 AM, Bill Speirs <bill.speirs@gmail.com> wrote:
>> >>
>> >> I don't think this is supported (but I could be compl= etely wrong).
>> >> However, I'd love to see this functionality as well.<= br> >> >>
>> >> How would one go about requesting such a feature?
>> >>
>> >> Bill-
>> >>
>> >> On Mon, Feb 7, 2011 at 4:15 PM, Kallin Nagelberg
>> >> <kallin.= nagelberg@gmail.com> wrote:
>> >>> Hey,
>> >>>
>> >>> I have read about the new TTL columns in Cassandra 0.= 7. In my case I'd
>> >>> like to expire an entire row automatically after a ce= rtain amount of
>> >>> time. Is this possible as well?
>> >>>
>> >>> Thanks,
>> >>> -Kal
>> >>>
>> >>
>> >
>
>

--90e6ba4fc4b696bd67049bc6dc92--