cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maxim Potekhin <potek...@bnl.gov>
Subject Re: Implications of length of column names
Date Tue, 28 Feb 2012 23:06:32 GMT
When I migrated data from our RDBMS, I hashed columns names to integers. 
This makes for some
footwork, but the space gain is clearly there so it's worth it. I 
de-hash on read.

Maxim


On 2/10/2012 5:15 PM, Narendra Sharma wrote:
> 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 
> <mailto: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//
>
>


Mime
View raw message