Return-Path: Delivered-To: apmail-cassandra-dev-archive@www.apache.org Received: (qmail 93198 invoked from network); 29 Sep 2010 05:14:57 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 29 Sep 2010 05:14:57 -0000 Received: (qmail 90355 invoked by uid 500); 29 Sep 2010 05:14:57 -0000 Delivered-To: apmail-cassandra-dev-archive@cassandra.apache.org Received: (qmail 89918 invoked by uid 500); 29 Sep 2010 05:14:54 -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 89910 invoked by uid 99); 29 Sep 2010 05:14:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Sep 2010 05:14:53 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jbellis@gmail.com designates 209.85.216.172 as permitted sender) Received: from [209.85.216.172] (HELO mail-qy0-f172.google.com) (209.85.216.172) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Sep 2010 05:14:47 +0000 Received: by qyk31 with SMTP id 31so499885qyk.10 for ; Tue, 28 Sep 2010 22:14:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=W8S4kjzlgASA79BDLOknxpD7XCdod0cfp9ugedy3NLo=; b=SO8Bq69b5G6DH5MI3rUg+qLmYWHM5866Hq1JlUablDasqPb3Vz4fuM7Z8XVA+RdXX/ 1RsN654cxerBd8Yl1RJtc0Ki8WZfa0aPmH5c701zQalATWgKQ6qT9NICtACDJXByZvoa b7AanGvVSXD+xkhbnnWxOei8cWw5vf6b5XUC0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=TB9Aa7ivusswnR8VbSDwvceJFxLfHWfyk9cOeMwvxF1rsrmLGD2b2qqKh26YwWYdmY 9UpR0dKy4UpietAAFNUzMh3YozVv5xYf7NC7L8w5zi2AacZ3BZ4vZ4HO8wupcFjmW3I3 v9s4YVHduW0HsRpu2ro1d6lvT+6RHQhY+0FJI= MIME-Version: 1.0 Received: by 10.220.4.19 with SMTP id 19mr217138vcp.263.1285737265813; Tue, 28 Sep 2010 22:14:25 -0700 (PDT) Received: by 10.220.186.132 with HTTP; Tue, 28 Sep 2010 22:14:25 -0700 (PDT) In-Reply-To: References: <3CCCC121-BD60-4D3B-B7AA-353CEAB9C241@oskarsson.nu> <4C0416C5-6422-48D0-9055-092543C47C42@oskarsson.nu> <0073704B-BDD4-44D1-8CCD-44C9B084A3EF@gmail.com> Date: Wed, 29 Sep 2010 00:14:25 -0500 Message-ID: Subject: Re: [DISCUSSION] High-volume counters in Cassandra From: Jonathan Ellis To: dev Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On Tue, Sep 28, 2010 at 4:00 PM, Sylvain Lebresne wrote: > I agree that it is worth adding a support for counter as supercolumns > in 1546 and that's fairly trivial, so I will add that as soon as possible > (but please understand that I'm working on this for a good part during > my free time). > > As for supercolumns of counters, there is what Jonathan proposes, but > I'll add that encoding a supercolumns CF to a standard column CF is > almost always a fairly trivial encoding. Worst case scenario it requires > you to roll up your own comparator and it's slightly less convenient > for client code. Supporting supercolumns to allow multiple counters per row, but requiring encoding with a custom comparator for deeper nesting, seems like a reasonable compromise to me. Ryan, while this obviously isn't ideal from your perspective of already having code written against supercolumns-of-counters, is it something you could live with? In exchange we get 1072 + 1210 + 1397 + 1375 + ConsistencyLevel support for substantially less code (= less complexity and special cases) than 1072 alone. -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of Riptano, the source for professional Cassandra support http://riptano.com