cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maxim Potekhin <>
Subject Re: Doubts related to composite type column names/values
Date Tue, 20 Dec 2011 18:43:53 GMT
With regards to static, what are major benefits as it compares with
string catenation (with some convenient separator inserted)?



On 12/20/2011 1:39 PM, Richard Low wrote:
> On Tue, Dec 20, 2011 at 5:28 PM, Ertio Lew<>  wrote:
>> With regard to the composite columns stuff in Cassandra, I have the
>> following doubts :
>> 1. What is the storage overhead of the composite type column names/values,
> The values are the same.  For each dimension, there is 3 bytes overhead.
>> 2. what exactly is the difference between the DynamicComposite and Static
>> Composite ?
> Static composite type has the types of each dimension specified in the
> column family definition, so all names within that column family have
> the same type.  Dynamic composite type lets you specify the type for
> each column, so they can be different.  There is extra storage
> overhead for this and care must be taken to ensure all column names
> remain comparable.

View raw message