From user-return-31695-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Thu Feb 7 04:08:58 2013 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 D5F9CE9B6 for ; Thu, 7 Feb 2013 04:08:58 +0000 (UTC) Received: (qmail 82294 invoked by uid 500); 7 Feb 2013 04:08:55 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 82165 invoked by uid 500); 7 Feb 2013 04:08:55 -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 82081 invoked by uid 99); 7 Feb 2013 04:08:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Feb 2013 04:08:52 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [208.113.200.5] (HELO homiemail-a91.g.dreamhost.com) (208.113.200.5) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Feb 2013 04:08:47 +0000 Received: from homiemail-a91.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a91.g.dreamhost.com (Postfix) with ESMTP id A16C6AE05B for ; Wed, 6 Feb 2013 20:08:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thelastpickle.com; h=from :content-type:message-id:mime-version:subject:date:references:to :in-reply-to; s=thelastpickle.com; bh=w6mcLG3lgN/92lkcHifJXuh2p7 A=; b=k4QvI3AMEig1NRxT5wvEa6O/2R1beBEoBbJokO6oWYbsjYQ0b6XyGLjOe0 8csRvBWfomx8Ijx++hJVUiRXmq3NbsFt9s/NP2zRpKprh6MKPFZESP4ZM+2HcyA4 O+LEsL8yirIsHCD3ORRM1oQ5n/EDDwiIux+TAMQajOoI6MCfw= Received: from [172.16.1.8] (unknown [203.86.207.101]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: aaron@thelastpickle.com) by homiemail-a91.g.dreamhost.com (Postfix) with ESMTPSA id E8669AE059 for ; Wed, 6 Feb 2013 20:08:14 -0800 (PST) From: aaron morton Content-Type: multipart/alternative; boundary="Apple-Mail=_6F63146F-C53B-4360-AF7F-2B1FBF22FB04" Message-Id: <912E6E30-F356-4656-B3AB-998C7E05618F@thelastpickle.com> Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: Operation Consideration with Counter Column Families Date: Thu, 7 Feb 2013 17:08:24 +1300 References: <2608F151-F38D-4010-991F-478A5D172A9C@venarc.com> <126B9DC3-37B3-4DB1-8061-5ECB8A250201@venarc.com> To: user@cassandra.apache.org In-Reply-To: <126B9DC3-37B3-4DB1-8061-5ECB8A250201@venarc.com> X-Mailer: Apple Mail (2.1499) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_6F63146F-C53B-4360-AF7F-2B1FBF22FB04 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > Thanks Aaron, so will there only be one "value" for each counter = column per sstable just like regular columns? Yes.=20 > For some reason I was under the impression that Cassandra keeps a log = of all the increments not the actual value. Not as far as I understand.=20 Cheers =20 ----------------- Aaron Morton Freelance Cassandra Developer New Zealand @aaronmorton http://www.thelastpickle.com On 6/02/2013, at 11:15 AM, Drew Kutcharian wrote: > Thanks Aaron, so will there only be one "value" for each counter = column per sstable just like regular columns? For some reason I was = under the impression that Cassandra keeps a log of all the increments = not the actual value. >=20 >=20 > On Feb 5, 2013, at 12:36 PM, aaron morton = wrote: >=20 >>> Are there any specific operational considerations one should make = when using counter columns families? >> Performance, as they incur a read and a write.=20 >> There were some issues with overcounts in log replay (see the = changes.txt).=20 >> =20 >>> How are counter column families stored on disk?=20 >> Same as regular CF's.=20 >>=20 >>> How do they effect compaction? >> None. >>=20 >> Cheers >>=20 >> ----------------- >> Aaron Morton >> Freelance Cassandra Developer >> New Zealand >>=20 >> @aaronmorton >> http://www.thelastpickle.com >>=20 >> On 6/02/2013, at 7:47 AM, Drew Kutcharian wrote: >>=20 >>> Hey Guys, >>>=20 >>> Are there any specific operational considerations one should make = when using counter columns families? How are counter column families = stored on disk? How do they effect compaction? >>>=20 >>> -- Drew >>>=20 >>=20 >=20 --Apple-Mail=_6F63146F-C53B-4360-AF7F-2B1FBF22FB04 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
Yes. 

 For some reason I = was under the impression that Cassandra keeps a log of all the = increments not the actual value.
Not as far as I = understand. 

Cheers
 
http://www.thelastpickle.com

On 6/02/2013, at 11:15 AM, Drew Kutcharian <drew@venarc.com> wrote:

Thanks Aaron, so = will there only be one "value" for each counter column per = sstable just like regular columns? For some reason I was under the = impression that Cassandra keeps a log of all the increments not the = actual value.


On Feb 5, 2013, at 12:36 = PM, aaron morton <aaron@thelastpickle.com> = wrote:

Are there any specific operational = considerations one should make when using counter columns = families?
Performance, as they incur a read and a = write. 
There were some issues with overcounts in log replay = (see the changes.txt). 
 
 How are counter column families stored on = disk? 
Same as regular = CF's. 

How do = they effect = compaction?
None.

Cheers
http://www.thelastpickle.com

On 6/02/2013, at 7:47 AM, Drew Kutcharian <drew@venarc.com> wrote:

Hey = Guys,

Are there any specific operational considerations one = should make when using counter columns families? How are counter column = families stored on disk? How do they effect compaction?

-- = Drew




= --Apple-Mail=_6F63146F-C53B-4360-AF7F-2B1FBF22FB04--