Return-Path: 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 A2F339BC1 for ; Tue, 3 Jan 2012 19:58:40 +0000 (UTC) Received: (qmail 74259 invoked by uid 500); 3 Jan 2012 19:58:38 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 74226 invoked by uid 500); 3 Jan 2012 19:58:38 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 74217 invoked by uid 99); 3 Jan 2012 19:58:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jan 2012 19:58:38 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rajkumar.w93@gmail.com designates 74.125.82.172 as permitted sender) Received: from [74.125.82.172] (HELO mail-we0-f172.google.com) (74.125.82.172) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jan 2012 19:58:31 +0000 Received: by werb14 with SMTP id b14so9600510wer.31 for ; Tue, 03 Jan 2012 11:58:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=8camYpF4D8zr2EGihXGdBusj+Wm4c0HWW+yOEaz3o24=; b=tr8k6yXuSlf4L1KNNIeZzjrtBEkbjDzj4Q1kziEIUPXBZcwfwV1mdG0H/+i+rQEU/f 3rpB9cR/sv+8wFM6MceQ18wt9DbC7quRooYw2KuYPxcDDzY3T/T2gANk8rKCqZ3hHh7h bdX/nhovWSpFnajTsY0nRjVB+zZp3hJ0kHTzo= MIME-Version: 1.0 Received: by 10.216.143.206 with SMTP id l56mr35878690wej.46.1325620690456; Tue, 03 Jan 2012 11:58:10 -0800 (PST) Sender: rajkumar.w93@gmail.com Received: by 10.223.143.72 with HTTP; Tue, 3 Jan 2012 11:58:10 -0800 (PST) Date: Wed, 4 Jan 2012 01:28:10 +0530 X-Google-Sender-Auth: jev-LtZNYqmMlqpbCMMxd54FWQ0 Message-ID: Subject: Replacing supercolumns with composite columns; Getting the equivalent of retrieving a list of supercolumns by name From: Asil Klin To: user Content-Type: multipart/alternative; boundary=0016e6d626a85c912d04b5a51e65 --0016e6d626a85c912d04b5a51e65 Content-Type: text/plain; charset=ISO-8859-1 I have a super columns family which I always use to retrieve a list of supercolumns(with all subcolumns) by name. I am looking forward to replace all SuperColumns in my schema with the composite columns. How could I design schema so that I could do the equivalent of retrieving a list of supercolumns by name, in case of using composite columns. (As of now I thought of using the supercolumn name as the first component of the composite name and the subcolumn name as 2nd component of composite name.) --0016e6d626a85c912d04b5a51e65 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I have a super columns family which I always use to retrieve a list of supe= rcolumns(with all subcolumns) by name. I am looking forward to replace all = SuperColumns in my schema with the composite columns.

How could I design schema so that I could do the equivalent of=A0retrieving= =A0a list of supercolumns by name, in case of using composite columns.=A0

(As of now I thought of using the supercolumn name = as the first component of the composite name and the subcolumn name as 2nd = component of composite name.)
--0016e6d626a85c912d04b5a51e65--