Return-Path: Delivered-To: apmail-cassandra-dev-archive@www.apache.org Received: (qmail 22614 invoked from network); 28 Sep 2010 20:15:59 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 28 Sep 2010 20:15:59 -0000 Received: (qmail 63417 invoked by uid 500); 28 Sep 2010 19:49:19 -0000 Delivered-To: apmail-cassandra-dev-archive@cassandra.apache.org Received: (qmail 63355 invoked by uid 500); 28 Sep 2010 19:49:19 -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 63344 invoked by uid 99); 28 Sep 2010 19:49:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Sep 2010 19:49:18 +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 (athena.apache.org: domain of jbellis@gmail.com designates 209.85.160.44 as permitted sender) Received: from [209.85.160.44] (HELO mail-pw0-f44.google.com) (209.85.160.44) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Sep 2010 19:49:14 +0000 Received: by pwi3 with SMTP id 3so22731pwi.31 for ; Tue, 28 Sep 2010 12:48:54 -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=hqDBaN+pH+EcgT6anidLcBDR+o8R4y2MHf9gMByK9Lo=; b=LM1BJChO/EMOA3jvXhal9aBFrn1C7BloSOexI5QzStqmkApmKVhBs5VeNRdw+IAFpZ 2i/zkNnkxWwmdfM27weNmrObJmgWIpkEkfudG3Q9G0b/uyiPYpPg0YDqCyOy9O1EMP/f z3f6/XCSb7PKc1pq3WhactYIrlqkNlm5d00lU= 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=EfcNrEUJPHytEBEfH+OrCOHSrC2aaJTnv6wmOuqkL3fj20Ob0AyqDjer9wEuHCzX8r RFkCYRlTgViRHKY8pr3TSf5UUOnYqIsFZX9L+PU6oZnenw4Zw5fdGQshMt5sbe1Xgwif NTsad6uiHMON5Ehxw8z0S3+Dkf+QckV+TSPxs= MIME-Version: 1.0 Received: by 10.142.239.21 with SMTP id m21mr422904wfh.266.1285703334056; Tue, 28 Sep 2010 12:48:54 -0700 (PDT) Received: by 10.220.186.132 with HTTP; Tue, 28 Sep 2010 12:48:53 -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: Tue, 28 Sep 2010 14:48:53 -0500 Message-ID: Subject: Re: [DISCUSSION] High-volume counters in Cassandra From: Jonathan Ellis To: dev Content-Type: text/plain; charset=ISO-8859-1 On Tue, Sep 28, 2010 at 2:25 PM, Ryan King wrote: > Sorry, been catching up on this. > > From Twitter's perspective, 1546 is probably insufficient because it > doesn't allow one to do time-series data without supercolumns (which > might work ok, but require a good deal of work). Additionally, one of > our deployed systems already does supercolumns of counters, which is > not feasible in this design at all. True, although wouldn't rows-of-counters give you basically the same thing if 1546 kept its counters as subcolumns of a supercolumn? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of Riptano, the source for professional Cassandra support http://riptano.com