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 7E67C6D21 for ; Wed, 13 Jul 2011 20:31:35 +0000 (UTC) Received: (qmail 41060 invoked by uid 500); 13 Jul 2011 20:31:33 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 41010 invoked by uid 500); 13 Jul 2011 20:31:32 -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 41002 invoked by uid 99); 13 Jul 2011 20:31:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jul 2011 20:31:32 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,MIME_QP_LONG_LINE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [208.113.200.5] (HELO homiemail-a40.g.dreamhost.com) (208.113.200.5) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jul 2011 20:31:24 +0000 Received: from homiemail-a40.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a40.g.dreamhost.com (Postfix) with ESMTP id A518774C057 for ; Wed, 13 Jul 2011 13:31:01 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; c=nofws; d=thelastpickle.com; h=subject :references:from:content-type:in-reply-to:message-id:date:to :content-transfer-encoding:mime-version; q=dns; s= thelastpickle.com; b=RdazBczCQXlBMa2ZW4Un3wAAhY4XN/g+qFmGZy2yLM/ yeM5ds9zTACVeKuOj+Mgn6vjpD+CGqM5R170LPz5FnL/jOjOyz+Swu/9BI0I/6YN alSdKwhHuAxEP7n26yxXtidFytfMAFVkSV7ZEcJ6SxqiKDbwTn2E/n/N6ZEViRRg = DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thelastpickle.com; h= subject:references:from:content-type:in-reply-to:message-id:date :to:content-transfer-encoding:mime-version; s=thelastpickle.com; bh=4yv6u4vjYOX97hNbA9IML8bxkAM=; b=QTkjo0KniUCFw+5UU3ah6tNHFtZW fmYfjQQVgGCO2B5wRoURWUt0ZeDbhrl9LdqS8srZDpsSd5hyhje2hYZ0e1FvRfCO 88fqJMNsh1rNJg4l8ELyqLANqMtFTRTTuJI9ZvoVbdWnpLwbQaQlMAfT3L0xhazY LDSybyzAyv9JyfY= Received: from [115.189.217.204] (unknown [115.189.217.204]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: aaron@thelastpickle.com) by homiemail-a40.g.dreamhost.com (Postfix) with ESMTPSA id 9463D74C06E for ; Wed, 13 Jul 2011 13:31:00 -0700 (PDT) Subject: Re: Storing counters in the standard column families along with non-counter columns ? References: <4E1B0CBD.8050200@gmail.com> From: Aaron Morton Content-Type: multipart/alternative; boundary=Apple-Mail-1--580123044 In-Reply-To: Message-Id: <63BE72D8-33A0-4854-9F39-F22ECC3462A0@thelastpickle.com> Date: Thu, 14 Jul 2011 07:57:21 +1200 To: "user@cassandra.apache.org" Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (iPad Mail 8J3) X-Mailer: iPad Mail (8J3) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail-1--580123044 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii If you can provide some more details on the use case we may be able to provi= de some data model help. You can always use a dedicated CF for the counters, and use the same row key= . Cheers ----------------- Aaron Morton Freelance Cassandra Developer @aaronmorton http://www.thelastpickle.com On 12/07/2011, at 6:36 AM, Aditya Narayan wrote: > Oops that's really very much disheartening and it could seriously impact o= ur plans for going live in near future. Without this facility I guess counte= rs currently have very little usefulness. >=20 > On Mon, Jul 11, 2011 at 8:16 PM, Chris Burroughs wrote: > On 07/10/2011 01:09 PM, Aditya Narayan wrote: > > Is there any target version in near future for which this has been promi= sed > > ? >=20 > The ticket is problematic in that it would -- unless someone has a > clever new idea -- require breaking thrift compatibility to add it to > the api. Since is unfortunate since it would be so useful. >=20 > If it's in the 0.8.x series it will only be through CQL. >=20 --Apple-Mail-1--580123044 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=utf-8
If you can provide some more details on the use case we may be able to provide some data model help.

You can always use a dedicated CF for the counters, and use the same row key.

Cheers


-----------------
Aaron Morton
Freelance Cassandra Developer
@aaronmorton

On 12/07/2011, at 6:36 AM, Aditya Narayan <adynnn@gmail.com> wrote:

Oops that's really very much disheartening and it could seriously impact our plans for going live in near future. Without this facility I guess counters currently have very little usefulness.

On Mon, Jul 11, 2011 at 8:16 PM, Chris Burroughs <chris.burroughs@gmail.com> wrote:
On 07/10/2011 01:09 PM, Aditya Narayan wrote:
> Is there any target version in near future for which this has been promised
> ?

The ticket is problematic in that it would -- unless someone has a
clever new idea -- require breaking thrift compatibility to add it to
the api.  Since is unfortunate since it would be so useful.

If it's in the 0.8.x series it will only be through CQL.

--Apple-Mail-1--580123044--