Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7E6FC624E for ; Sat, 28 May 2011 12:54:05 +0000 (UTC) Received: (qmail 76584 invoked by uid 500); 28 May 2011 12:54:03 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 76556 invoked by uid 500); 28 May 2011 12:54:03 -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 76548 invoked by uid 99); 28 May 2011 12:54:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 28 May 2011 12:54:03 +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.216.44] (HELO mail-qw0-f44.google.com) (209.85.216.44) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 28 May 2011 12:53:57 +0000 Received: by qwc23 with SMTP id 23so1672381qwc.31 for ; Sat, 28 May 2011 05:53:36 -0700 (PDT) Received: by 10.229.67.66 with SMTP id q2mr2213551qci.282.1306587216114; Sat, 28 May 2011 05:53:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.228.4 with HTTP; Sat, 28 May 2011 05:53:16 -0700 (PDT) In-Reply-To: References: From: =?UTF-8?Q?Utku_Can_Top=C3=A7u?= Date: Sat, 28 May 2011 14:53:16 +0200 Message-ID: Subject: Re: expiring + counter column? To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=0016363b7c12e2747e04a4558a89 X-Virus-Checked: Checked by ClamAV on apache.org --0016363b7c12e2747e04a4558a89 Content-Type: text/plain; charset=UTF-8 How about implementing a freezing mechanism on counter columns. If there are no more increments within "freeze" seconds after the last increments (it would be orders or day or so); the column would lock itself on increments and won't accept increment. And after this freeze perioid, the ttl should work fine. The column will be gone forever after freeze + ttl seconds. On Sat, May 28, 2011 at 2:57 AM, Jonathan Ellis wrote: > No. See comments to https://issues.apache.org/jira/browse/CASSANDRA-2103 > > On Fri, May 27, 2011 at 7:29 PM, Yang wrote: > > is this combination feature available , or on track ? > > > > thanks > > Yang > > > > > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder of DataStax, the source for professional Cassandra support > http://www.datastax.com > --0016363b7c12e2747e04a4558a89 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable How about implementing a freezing mechanism on counter columns.

If t= here are no more increments within "freeze" seconds after the las= t increments (it would be orders or day or so); the column would lock itsel= f on increments and won't accept increment.

And after this freeze perioid, the ttl should work fine. The column wil= l be gone forever after freeze + ttl seconds.

On Sat, May 28, 2011 at 2:57 AM, Jonathan Ellis <= jbellis@gmail.com> wrote= :
No. See comments = to https://issues.apache.org/jira/browse/CASSANDRA-2103

On Fri, May 27, 2011 at 7:29 PM, Yang <teddyyyy123@gmail.com> wrote:
> is this combination feature available , or on track ?
>
> thanks
> Yang
>



--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.c= om

--0016363b7c12e2747e04a4558a89--