Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 61319 invoked from network); 13 Feb 2011 20:18:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 13 Feb 2011 20:18:51 -0000 Received: (qmail 3961 invoked by uid 500); 13 Feb 2011 20:18:49 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 3903 invoked by uid 500); 13 Feb 2011 20:18:48 -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 3895 invoked by uid 99); 13 Feb 2011 20:18:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 13 Feb 2011 20:18:48 +0000 X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests=MIME_QP_LONG_LINE,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-a81.g.dreamhost.com) (208.113.200.5) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 13 Feb 2011 20:18:42 +0000 Received: from homiemail-a81.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a81.g.dreamhost.com (Postfix) with ESMTP id B3AA5A8061 for ; Sun, 13 Feb 2011 12:18:21 -0800 (PST) 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=fgJbNyIiwnsTb9V+ZU4AVTXuCUHpTjupf2RMi/lSdv4 UiY9O4djRc0ETvrVDms5rek5ME0rzWkiBgXuG/E3AMHgR1pwgHatZCNcKWmyGn9U BzrYcwl+8UTBV2+QP24duPsXUFy0hLd7sZJzXdchT4jDVhm1KkJO0DMIicRgxMgk = 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=wSUGMhaSGGKAypxHbQW26IBQ/ZA=; b=y0fAClI13ri/Pd3vwI7EAPuZ0Qt3 qNlJj81zq8QFfp3pFaVZvvnk1SXGju+1bclMBrnmHWf57sr+wTXonzUqyH8dXFA+ 3xkiJe5jeZGJKwALYyGBxkbAlc6IUXRXrc6VIgSt1MVBT1gMACAMFHLMGF17R7Df l7Ju3q+k3vRzZ/E= Received: from [115.189.234.109] (unknown [115.189.234.109]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: aaron@thelastpickle.com) by homiemail-a81.g.dreamhost.com (Postfix) with ESMTPSA id AD8E4A805C for ; Sun, 13 Feb 2011 12:18:20 -0800 (PST) Subject: Re: Column name size References: <4D556229.8040602@gmail.com> From: Aaron Morton Content-Type: text/plain; charset=us-ascii X-Mailer: iPad Mail (8C148) In-Reply-To: <4D556229.8040602@gmail.com> Message-Id: <160571FD-A40E-43D4-8D3F-49A01C491CF2@thelastpickle.com> Date: Mon, 14 Feb 2011 09:18:08 +1300 To: "user@cassandra.apache.org" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (iPad Mail 8C148) FWIW I would first try to reduce the number of columns, before reducing thei= r name length. If you always pull back the same columns (e.g. User details) c= onsider packing them in json dict and storing them in one column. Aaron On 12/02/2011, at 5:22 AM, Chris Burroughs wrote= : > On 02/11/2011 05:06 AM, Patrik Modesto wrote: >> Hi all! >>=20 >> I'm thinking if size of a column name could matter for a large dataset >> in Cassandra (I mean lots of rows). For example what if I have a row >> with 10 columns each has 10 bytes value and 10 bytes name. Do I have >> half the row size just of the column names and the other half of the >> data (not counting storage overhead)? What if I have 10M of these >> rows? Is there a difference? Should I use some 3bytes codes for a >> column name to save memory/bandwidth? >>=20 >> Thanks, >> Patrik >=20 > You are correct that you can for small row/column key values they key > itself can represent a large proportion of the total size. I think you > will find the consensus on this list is that trying to be clever with > names is usually not worth the additional complexity. >=20 > The right solution to this is > https://issues.apache.org/jira/browse/CASSANDRA-47.