Return-Path: 
 <user-return-16473-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org>
X-Original-To: apmail-cassandra-user-archive@www.apache.org
Delivered-To: apmail-cassandra-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 6C703275C
	for <apmail-cassandra-user-archive@www.apache.org>;
 Thu,  5 May 2011 14:53:59 +0000 (UTC)
Received: (qmail 63083 invoked by uid 500); 5 May 2011 14:53:57 -0000
Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org
Received: (qmail 63048 invoked by uid 500); 5 May 2011 14:53:57 -0000
Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@cassandra.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@cassandra.apache.org>
List-Post: <mailto:user@cassandra.apache.org>
List-Id: <user.cassandra.apache.org>
Reply-To: user@cassandra.apache.org
Delivered-To: mailing list user@cassandra.apache.org
Received: (qmail 63040 invoked by uid 99); 5 May 2011 14:53:57 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 May 2011 14:53:57 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of sylvain@datastax.com
 designates 209.85.213.44 as permitted sender)
Received: from [209.85.213.44] (HELO mail-yw0-f44.google.com) (209.85.213.44)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 May 2011 14:53:50 +0000
Received: by ywi6 with SMTP id 6so954309ywi.31
        for <user@cassandra.apache.org>; Thu, 05 May 2011 07:53:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.197.19 with SMTP id u19mr2459726ybf.327.1304607209293;
 Thu, 05 May 2011 07:53:29 -0700 (PDT)
Received: by 10.147.99.2 with HTTP; Thu, 5 May 2011 07:53:29 -0700 (PDT)
X-Originating-IP: [88.183.33.171]
In-Reply-To: <BANLkTi=WUJZo89yuYrTKGkkBv==qkEP-ZQ@mail.gmail.com>
References: <BANLkTi=WUJZo89yuYrTKGkkBv==qkEP-ZQ@mail.gmail.com>
Date: Thu, 5 May 2011 16:53:29 +0200
Message-ID: <BANLkTikUUuw9sotWyU=8D2bw8bTJm8D3xw@mail.gmail.com>
Subject: Re: Compound columns spec
From: Sylvain Lebresne <sylvain@datastax.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1

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:
*   <component><component><component> ...
* where <component> is:
*   <length of value><value><'end-of-component' byte>
* where the 'end-of-component' byte should always be 0 for actual column
* name.  However, it can set to 1 for query bounds. This allows to query for
* the equivalent of 'give me the full super-column'. That is, if during a
* slice query uses:
*   start = <3><"foo".getBytes()><0>
*   end   = <3><"foo".getBytes()><1>
* then he will be sure to get *all* the columns whose first component is "foo".
* If for a component, the 'end-of-component' is != 0, there should not be any
* following component.
*/

I'll mention that this is not committed code yet (but soon hopefully
and the format
shouldn't change).

--
Sylvain

On Thu, May 5, 2011 at 4:44 PM, David Boxenhorn <david@taotown.com> 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)?
>