On Thu, May 5, 2011 at 5:21 PM, David Boxenhorn wrote:
> What is the format of ?
With the warning of my previous mail, it's an unsigned short (2 bytes).
>
> On Thu, May 5, 2011 at 6:14 PM, Eric Evans wrote:
>>
>> On Thu, 2011-05-05 at 17:44 +0300, David Boxenhorn wrote:
>> > Is there a spec fo
I think for CQL there is two different things:
1) how the request will look like. I think that it is what Eric is
refering to when he says "colon delimited". So a query will
look like "SELECT foo:42:bar "
2) and there is the actual byte format in which the column name will
What is the format of ?
On Thu, May 5, 2011 at 6:14 PM, Eric Evans wrote:
> On Thu, 2011-05-05 at 17:44 +0300, David Boxenhorn wrote:
> > Is there a spec for compound columns?
> >
> > I want to know the exact format of compound columns so I can adhere to
> > it. For example, what is the separat
On Thu, 2011-05-05 at 17:44 +0300, David Boxenhorn wrote:
> Is there a spec for compound columns?
>
> I want to know the exact format of compound columns so I can adhere to
> it. For example, what is the separator - or is some other format used
> (e.g. length:value or type:length:value)?
Tentati
Thanks, yes, I was referring to the "compound columns" in this quote (from a
previous thread):
"No CQL will never support super columns, but later versions (not 1.0.0)
will support compound columns. Compound columns are better; instead of
a two-deep structure, you can have one of arbitrary depth.
I suppose it depends what you are referring to by "compound columns".
If you're talking
about the CompositeType of CASSANDRA-2231 (which is my only guess), then the
format is in the javadoc and is:
/*
* The encoding of a CompositeType column name should be:
*...
* where is:
* <'end-of-compon
Is there a spec for compound columns?
I want to know the exact format of compound columns so I can adhere to it.
For example, what is the separator - or is some other format used (e.g.
length:value or type:length:value)?
