Return-Path: Delivered-To: apmail-cassandra-dev-archive@www.apache.org Received: (qmail 90746 invoked from network); 30 Sep 2010 16:29:57 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 30 Sep 2010 16:29:57 -0000 Received: (qmail 59617 invoked by uid 500); 30 Sep 2010 16:29:56 -0000 Delivered-To: apmail-cassandra-dev-archive@cassandra.apache.org Received: (qmail 59530 invoked by uid 500); 30 Sep 2010 16:29:56 -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 59522 invoked by uid 99); 30 Sep 2010 16:29:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Sep 2010 16:29:55 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ryan@twitter.com designates 74.125.82.44 as permitted sender) Received: from [74.125.82.44] (HELO mail-ww0-f44.google.com) (74.125.82.44) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Sep 2010 16:29:51 +0000 Received: by wwj40 with SMTP id 40so77963wwj.25 for ; Thu, 30 Sep 2010 09:29:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.227.145.203 with SMTP id e11mr3363180wbv.134.1285864168778; Thu, 30 Sep 2010 09:29:28 -0700 (PDT) Received: by 10.227.134.203 with HTTP; Thu, 30 Sep 2010 09:29:27 -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: Thu, 30 Sep 2010 09:29:27 -0700 Message-ID: Subject: Re: [DISCUSSION] High-volume counters in Cassandra From: Ryan King To: dev@cassandra.apache.org Content-Type: text/plain; charset=ISO-8859-1 On Tue, Sep 28, 2010 at 10:14 PM, Jonathan Ellis wrote: > 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. I don't understand how this would work. -ryan