RE: sstable writer and creating bytebuffers

2015-03-31 Thread Peer, Oded
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

Re: sstable writer and creating bytebuffers

2015-03-31 Thread Sylvain Lebresne
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

RE: sstable writer and creating bytebuffers

2015-03-30 Thread Peer, Oded
@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

Re: sstable writer and creating bytebuffers

2015-03-30 Thread Sylvain Lebresne
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