Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of narendra.sharma@gmail.com
 designates 209.85.210.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1529B2A5-D11D-4661-8EB3-C71A624257AD@venarc.com>
References: <1529B2A5-D11D-4661-8EB3-C71A624257AD@venarc.com>
Date: Fri, 10 Feb 2012 14:15:12 -0800
Message-ID: 
 <CAHamXHGWrDB-iw-bbvLZBhEyu1G23HdjSeLQb1uG4AHo47B8zA@mail.gmail.com>
Subject: Re: Implications of length of column names
From: Narendra Sharma <narendra.sharma@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=90e6ba1efdd664ccee04b8a376fa

--90e6ba1efdd664ccee04b8a376fa
Content-Type: text/plain; charset=ISO-8859-1

It is good to have short column names. They save space all the way from
network transfer to in-memory usage to storage. It is also good idea to
club immutables columns that are read together and store as single column.
We gained significant overall performance benefits with this.

-Naren

On Fri, Feb 10, 2012 at 12:20 PM, Drew Kutcharian <drew@venarc.com> wrote:

> What are the implications of using short vs long column names? Is it
> better to use short column names or longer ones?
>
> I know for MongoDB you are better of using short field names
> http://www.mongodb.org/display/DOCS/Optimizing+Storage+of+Small+Objects
>  Does this apply to Cassandra column names?
>
>
> -- Drew
>


-- 
Narendra Sharma
Software Engineer
*http://www.aeris.com <http://www.persistentsys.com>*
*http://narendrasharma.blogspot.com/*

--90e6ba1efdd664ccee04b8a376fa
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

It is good to have short column names. They save space all the way from net=
work transfer to in-memory usage to storage. It is also good idea to club i=
mmutables columns that are read together and store as single column. We gai=
ned significant overall performance benefits with this.<div>
<br></div><div>-Naren</div><div><br><div class=3D"gmail_quote">On Fri, Feb =
10, 2012 at 12:20 PM, Drew Kutcharian <span dir=3D"ltr">&lt;<a href=3D"mail=
to:drew@venarc.com">drew@venarc.com</a>&gt;</span> wrote:<br><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex">
<div style=3D"word-wrap:break-word">What are the implications of using shor=
t vs long column names? Is it better to use short column names or longer on=
es?<div><br></div><div>I know for MongoDB you are better of using short fie=
ld names=A0<a href=3D"http://www.mongodb.org/display/DOCS/Optimizing+Storag=
e+of+Small+Objects" target=3D"_blank">http://www.mongodb.org/display/DOCS/O=
ptimizing+Storage+of+Small+Objects</a>=A0 =A0Does this apply to Cassandra c=
olumn names?</div>
<span class=3D"HOEnZb"><font color=3D"#888888"><div><br></div><div><br></di=
v><div>-- Drew</div></font></span></div></blockquote></div><br><br clear=3D=
"all"><div><br></div>-- <br><font color=3D"#999999">Narendra Sharma</font><=
div>
<font color=3D"#999999">Software Engineer</font><br><div><i><a href=3D"http=
://www.persistentsys.com" target=3D"_blank">http://www.aeris.com</a></i></d=
iv><div><i><a href=3D"http://narendrasharma.blogspot.com/" target=3D"_blank=
">http://narendrasharma.blogspot.com/</a></i></div>
<div><br></div></div><br>
</div>

--90e6ba1efdd664ccee04b8a376fa--