From user-return-13587-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Thu Feb 17 17:19:58 2011 Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 80466 invoked from network); 17 Feb 2011 17:19:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Feb 2011 17:19:58 -0000 Received: (qmail 62347 invoked by uid 500); 17 Feb 2011 17:19:56 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 62125 invoked by uid 500); 17 Feb 2011 17:19:53 -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 62116 invoked by uid 99); 17 Feb 2011 17:19:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Feb 2011 17:19:52 +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 (athena.apache.org: local policy) Received: from [209.85.216.44] (HELO mail-qw0-f44.google.com) (209.85.216.44) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Feb 2011 17:19:48 +0000 Received: by qwi2 with SMTP id 2so2821331qwi.31 for ; Thu, 17 Feb 2011 09:19:27 -0800 (PST) Received: by 10.229.245.1 with SMTP id ls1mr2636344qcb.13.1297963166551; Thu, 17 Feb 2011 09:19:26 -0800 (PST) MIME-Version: 1.0 Received: by 10.229.87.201 with HTTP; Thu, 17 Feb 2011 09:19:06 -0800 (PST) In-Reply-To: References: From: =?UTF-8?Q?Utku_Can_Top=C3=A7u?= Date: Thu, 17 Feb 2011 18:19:06 +0100 Message-ID: Subject: Re: Does counter columns support TTL To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=0016363b8b88794f85049c7d99de --0016363b8b88794f85049c7d99de Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable And I think this patch would still be useful and legitimate if the TTL of the initial increment is taken into account. On Thu, Feb 17, 2011 at 6:11 PM, Utku Can Top=C3=A7u wr= ote: > Yes, I've read the discussion. My use-case is similar to the use-case of > the contributor. > > So that's the reason why I've asked if it works or not. (with the flaw of > course). > > > > > On Thu, Feb 17, 2011 at 5:41 PM, Jonathan Ellis wrote= : > >> If you read the discussion on that ticket, the point is that the >> approach is fundamentally flawed. >> >> On Thu, Feb 17, 2011 at 10:16 AM, Utku Can Top=C3=A7u >> wrote: >> > Can anyone confirm that this patch works with the current trunk? >> > >> > On Thu, Feb 17, 2011 at 4:16 PM, Sylvain Lebresne > > >> > wrote: >> >> >> >> https://issues.apache.org/jira/browse/CASSANDRA-2103 >> >> >> >> On Thu, Feb 17, 2011 at 4:05 PM, Utku Can Top=C3=A7u >> wrote: >> >>> >> >>> Hi All, >> >>> >> >>> I'm experimenting and developing using counters. However, I've come = to >> a >> >>> usecase where I need counters to expire and get deleted after a >> certain time >> >>> of inactivity (i.e. have countercolumn deleted one hour after the la= st >> >>> increment). >> >>> >> >>> As far as I can tell counter columns don't have TTL in the thrift >> >>> interface, is it because of a limitation of the counter >> implementation? >> >>> >> >>> Regards, >> >>> Utku >> >>> >> >>> >> >> >> > >> > >> >> >> >> -- >> Jonathan Ellis >> Project Chair, Apache Cassandra >> co-founder of Riptano, the source for professional Cassandra support >> http://riptano.com >> > > --0016363b8b88794f85049c7d99de Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable And I think this patch would still be useful and legitimate if the TTL of t= he initial increment is taken into account.


On Thu, Feb 17, 2011 at 6:11 PM, Utku Can Top=C3=A7u <utku@topcu.gen.tr> wrote:
Yes, I've rea= d the discussion. My use-case is similar to the use-case of the contributor= .

So that's the reason why I've asked if it works or not. (with t= he flaw of course).




On Thu, Feb 17, 2011 at 5:41 PM, Jonathan Ellis <jbellis@gmail.com>= wrote:
If you read the discussion on that ticket, the point is that the
approach is fundamentally flawed.

On Thu, Feb 17, 2011 at 10:16 AM, Utku Can Top=C3=A7u <utku@topcu.gen.tr> wrote:
> Can anyone confirm that this patch works with the current trunk?
>
> On Thu, Feb 17, 2011 at 4:16 PM, Sylvain Lebresne <sylvain@datastax.com>
> wrote:
>>
>> https://issues.apache.org/jira/browse/CASSANDRA-2103 >>
>> On Thu, Feb 17, 2011 at 4:05 PM, Utku Can Top=C3=A7u <utku@topcu.gen.tr> w= rote:
>>>
>>> Hi All,
>>>
>>> I'm experimenting and developing using counters. However, = I've come to a
>>> usecase where I need counters to expire and get deleted after = a certain time
>>> of inactivity (i.e. have countercolumn deleted one hour after = the last
>>> increment).
>>>
>>> As far as I can tell counter columns don't have TTL in the= thrift
>>> interface, is it because of a limitation of the counter implem= entation?
>>>
>>> Regards,
>>> Utku
>>>
>>>
>>
>
>



--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of Riptano, the source for professional Cassandra support
http://riptano.com


--0016363b8b88794f85049c7d99de--