I may have overcomplicated things.
In my opinion creating a CompositeType with a single type should throw an
exception.
From: Sylvain Lebresne [mailto:sylv...@datastax.com]
Sent: Tuesday, March 31, 2015 10:18 AM
To: user@cassandra.apache.org
Subject: Re: sstable writer and creating bytebuffers
hat in general, if you have only a single column, then there isn't too
much reasons to use a CompositeType.
--
Sylvain
>
>
>
> *From:* Sylvain Lebresne [mailto:sylv...@datastax.com]
> *Sent:* Monday, March 30, 2015 1:57 PM
> *To:* user@cassandra.apache.org
> *Subject:* Re
@cassandra.apache.org
Subject: Re: sstable writer and creating bytebuffers
No, it's not a bug. In a composite every elements start by a 2 short indicating
the size of the element, plus an extra byte that is used for sorting purposes.
A little bit more details can be found in the Composit
No, it's not a bug. In a composite every elements start by a 2 short
indicating the size of the element, plus an extra byte that is used for
sorting purposes. A little bit more details can be found in the
CompositeType class javadoc if you're interested. It's not the most compact
format there is bu
I am writing code to bulk load data into Cassandra using
SSTableSimpleUnsortedWriter
I changed my partition key from a composite key (long, int) to a single column
key (long).
For creating the composite key I used a CompositeType, and I kept using it
after changing the key to a single column.
My
