Return-Path: 
 <user-return-26511-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 62633932B
	for <apmail-cassandra-user-archive@www.apache.org>;
 Tue, 29 May 2012 10:09:37 +0000 (UTC)
Received: (qmail 17813 invoked by uid 500); 29 May 2012 10:09:35 -0000
Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org
Received: (qmail 17350 invoked by uid 500); 29 May 2012 10:09:31 -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 17323 invoked by uid 99); 29 May 2012 10:09:30 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 May 2012 10:09:30 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of cyril.auburtin@gmail.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; Tue, 29 May 2012 10:09:23 +0000
Received: by yhq56 with SMTP id 56so2525824yhq.31
        for <user@cassandra.apache.org>; Tue, 29 May 2012 03:09:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:from:date:message-id:subject:to:cc:content-type;
        bh=4pyvbemleODUx459g8yjRYQyYZXn8KevqIPMskB0A80=;
        b=X64QiOxYrz0zPTS7zsHZ2uBUKrONoUkBe+jJVlsHmlPddY6vdq2br55HqE9Xdc0La+
         5GDF/nWovmG1PJ7Bqjlsy0PxzhzK5e0OGGpgzoPAF8A2ul5hafegGczBbC+QhtQ2Vtxu
         Jo7iZfVsm/J5aiG1XqbYTDrbRvkY835gTHwLWVo4pCbVoPKE/yyAHJZSameVY7oQo/CT
         W4XVr2TZzCx+X6Nmx9vcjhBmGVIifQaCUZwOS5roPSBoNAWzZo/tKcYLIPJgu0NhK65y
         PgysaKYJfXFEzLPogrS5JQV1kLX8mzVkuZs7LrNuHb1KxyWSXCEhIGLZapBxHEp/5LFn
         xuww==
Received: by 10.236.145.104 with SMTP id o68mr10539195yhj.74.1338286142586;
 Tue, 29 May 2012 03:09:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.101.1.9 with HTTP; Tue, 29 May 2012 03:08:41 -0700 (PDT)
From: Cyril Auburtin <cyril.auburtin@gmail.com>
Date: Tue, 29 May 2012 12:08:41 +0200
Message-ID: 
 <CAKteAhHQNX88bvp2ehTk5q8GGiE8kOZW2DLQEFjhUxr1fC1UyA@mail.gmail.com>
Subject: About Composite range queries
To: user@cassandra.apache.org
Cc: Laurent Vanni <laurent.vanni@gmail.com>
Content-Type: multipart/alternative; boundary=20cf303b3cd923004d04c12a066e

--20cf303b3cd923004d04c12a066e
Content-Type: text/plain; charset=ISO-8859-1

How is it done in Cassandra to be able to range query on a composite key?

"key1" => (A:A:C), (A:B:C), (A:C:C), (A:D:C), (B,A,C)

like get_range ("key1", start_column=(A,"), end_column=(A, C)); will return
[ (A:B:C), (A:C:C) ] (in pycassa)

I mean does the composite implementation add much overhead to make it work?
Does it need to add other Column families, to be able to range query
between composites simple keys (first, second and third part of the
composite)?

What is the real advantage compared to super column families?

"key1" => A: (A,C), (B,C), (C,C), (D,C)  , B: (A,C)

thx

--20cf303b3cd923004d04c12a066e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

How is it done in Cassandra to be able to range query on a composite key?<d=
iv><br></div><div>&quot;key1&quot; =3D&gt; (A:A:C),=A0(A:B:C),=A0(A:C:C),=
=A0(A:D:C), (B,A,C)</div><div><br></div><div>like get_range (&quot;key1&quo=
t;, start_column=3D(A,&quot;), end_column=3D(A, C)); will return [=A0(A:B:C=
),=A0(A:C:C) ] (in pycassa)<br>

<div><br></div><div>I mean does the composite implementation add much overh=
ead to make it work?</div></div><div>Does it need to add other Column famil=
ies, to be able to range query between composites simple keys (first, secon=
d and third part of the composite)?</div>

<div><br></div><div>What is the real advantage compared to super column fam=
ilies?</div><div><br></div><div>&quot;key1&quot; =3D&gt; A: (A,C), (B,C), (=
C,C), (D,C) =A0, B: (A,C)</div><div><br></div><div>thx</div>

--20cf303b3cd923004d04c12a066e--