Return-Path: Delivered-To: apmail-cassandra-dev-archive@www.apache.org Received: (qmail 78354 invoked from network); 24 Sep 2010 12:10:48 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 24 Sep 2010 12:10:48 -0000 Received: (qmail 75313 invoked by uid 500); 24 Sep 2010 12:10:47 -0000 Delivered-To: apmail-cassandra-dev-archive@cassandra.apache.org Received: (qmail 75011 invoked by uid 500); 24 Sep 2010 12:10:44 -0000 Mailing-List: contact dev-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list dev@cassandra.apache.org Received: (qmail 75002 invoked by uid 99); 24 Sep 2010 12:10:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Sep 2010 12:10:43 +0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.215.44] (HELO mail-ew0-f44.google.com) (209.85.215.44) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Sep 2010 12:10:37 +0000 Received: by ewy26 with SMTP id 26so909778ewy.31 for ; Fri, 24 Sep 2010 05:10:16 -0700 (PDT) Received: by 10.213.7.7 with SMTP id b7mr3050575ebb.30.1285330216057; Fri, 24 Sep 2010 05:10:16 -0700 (PDT) Received: from [192.168.0.194] (90-227-195-50-no77.tbcn.telia.com [90.227.195.50]) by mx.google.com with ESMTPS id v59sm2985178eeh.10.2010.09.24.05.10.10 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 24 Sep 2010 05:10:11 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Apple Message framework v1081) Subject: Re: [DISCUSSION] High-volume counters in Cassandra From: Johan Oskarsson In-Reply-To: Date: Fri, 24 Sep 2010 14:10:06 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <3CCCC121-BD60-4D3B-B7AA-353CEAB9C241@oskarsson.nu> <4C0416C5-6422-48D0-9055-092543C47C42@oskarsson.nu> To: dev@cassandra.apache.org X-Mailer: Apple Mail (2.1081) Here is an update to where we are at with the counters. As promised we have published a new patch that adds a separate api = method, marked experimental, for the counters in CASSANDRA-1072. The discussion has now moved to CASSANDRA-1502, a ticket that suggests = the internal IClock, reconciler and other classes essential for 1072 = should be removed. Doing so would not only severely delay the addition = of counters to Cassandra but force a grounds up redesign of 1072 that we = believe would not improve the patch. This belief is based on the = prototyping Kelvin did for the work that has been refined into 1072. Since the overwhelming consensus of this discussion thread was that the = patch is valuable to the community and worthy of going in, we feel that = it should be committed in approximately its current form. While we work with the Apache community to resolve this issue we=92ve = decided to put up a temporary version of Cassandra that includes the = counters on the Twitter Github account. This is a step in releasing some of the systems we=92ve built on top of = this patch to the open source community in the near future. On 6 sep 2010, at 21.19, Jonathan Ellis wrote: > Yes. >=20 > On Mon, Sep 6, 2010 at 12:11 PM, Johan Oskarsson = wrote: >> The consensus in this thread seems to be moving towards the following = todos in order to get 1072 into trunk. >>=20 >> * create separate api methods for increments >> * mark functionality as experimental >> * further code cleanup (please comment on jira with specific = suggestions) >>=20 >> Is this a reasonable summary? We'll keep this thread updated as the = work progresses. >>=20 >> /Johan >>=20 >> On 6 sep 2010, at 16.47, Jonathan Ellis wrote: >>=20 >>> On Thu, Sep 2, 2010 at 4:10 PM, Torsten Curdt = wrote: >>>> The feature could still be marked experimental. >>>> That should loosen the contract a little. But at least it would be >>>> something to work with. >>>=20 >>> Maybe this is the best approach, post- code cleanup. Although I'm >>> reluctant to add code with known, significant limitations, the = problem >>> domain seems to be one with no silver bullets. >>=20 >>=20 >=20 >=20 >=20 > --=20 > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder of Riptano, the source for professional Cassandra support > http://riptano.com