Return-Path: 
 <user-return-34042-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 B0BA611948
	for <apmail-cassandra-user-archive@www.apache.org>;
 Sun, 12 May 2013 05:31:30 +0000 (UTC)
Received: (qmail 91875 invoked by uid 500); 12 May 2013 05:31:28 -0000
Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org
Received: (qmail 91823 invoked by uid 500); 12 May 2013 05:31:26 -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 91797 invoked by uid 99); 12 May 2013 05:31:25 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 12 May 2013 05:31:25 +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 (athena.apache.org: domain of eng.salamander@gmail.com
 designates 209.85.210.67 as permitted sender)
Received: from [209.85.210.67] (HELO mail-da0-f67.google.com) (209.85.210.67)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 12 May 2013 05:31:20 +0000
Received: by mail-da0-f67.google.com with SMTP id p8so765310dan.2
        for <user@cassandra.apache.org>; Sat, 11 May 2013 22:31:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:x-received:date:message-id:subject:from:to
         :content-type;
        bh=FouAuossxho4c5VVif1EHTtBfvEde4iJGnyndPaHmkU=;
        b=POSSbVD4SxW7e3xMA6ixlCHq9XVWrT4EN11eIL3GDHka5fDh19YyhhJGd1Gs1i5GOS
         okqDPW/SlqyZ4cVF1iwV1v2XIpxUa6rPN/pyCgqMm1HtbPJ1gdUxwZoeDYnKywrBevfm
         BGjqPZKK4ztK37+irQfPHXacMSZYLXbTj4fiB5O6z6345hqRXlwVJBbTLLtimpXMqi9z
         tdwCsbv0b5WlzR23lXSLpJ0o9Pj0lHdSadUrtn2f7wVqnTYvy9HdJV34u2S5oH+dGwHP
         nA7LnnpLJIvoThGfI+LHlJl0Pxsn0URYHC2nlAav093n/vxGv0DZ33MkGmAqiroCmvvR
         MYLg==
MIME-Version: 1.0
X-Received: by 10.66.156.196 with SMTP id wg4mr24615913pab.23.1368336660575;
 Sat, 11 May 2013 22:31:00 -0700 (PDT)
Received: by 10.70.30.65 with HTTP; Sat, 11 May 2013 22:31:00 -0700 (PDT)
Date: Sun, 12 May 2013 01:31:00 -0400
Message-ID: 
 <CAMAqzLXO2Fv_Zxh4aTPcgjXy5ojW-ms9BR8a74uCsgmCTzByXw@mail.gmail.com>
Subject: CQL3 Question
From: Sam Mandes <eng.salamander@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=047d7b86f1209639b504dc7eb41c
X-Virus-Checked: Checked by ClamAV on apache.org

--047d7b86f1209639b504dc7eb41c
Content-Type: text/plain; charset=ISO-8859-1

Hello All,

This is my first post here.

I noticed that Cassandra is pushing CQL3 more, it's even recommended to use
CQL3 for new projects instead of the Thrift API. I know that one can use
the compact storage to allow backward compatibility. And I know that CQL3
uses the new binary protocol instead of Thrift now. I believe they both use
the same storage engine. (I still do not understand why they are
incompatible!)

Thus, I was wondering is there is a possible way that I can view the tables
created with CQL3 in a lower-level view like I used with Thrift? I mean I
can view the tables as simply CFs, just something to expose the internal
representation.

Thanks a lot

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

<div dir=3D"ltr">Hello All,<div><br></div><div style>This is my first post =
here.</div><div style><br></div><div style>I noticed that Cassandra is push=
ing CQL3 more, it&#39;s even recommended to use CQL3 for new projects inste=
ad of the Thrift API. I know that one can use the compact storage to allow =
backward compatibility. And I know that CQL3 uses the new binary protocol i=
nstead of Thrift now. I believe they both use the same storage engine. (I s=
till do not understand why they are incompatible!)</div>
<div style><br></div><div style>Thus, I was wondering is there is a possibl=
e way that I can view the tables created with CQL3 in a lower-level view li=
ke I used with Thrift? I mean I can view the tables as simply CFs, just som=
ething to expose the internal representation.</div>
<div style><br></div><div style>Thanks a lot</div></div>

--047d7b86f1209639b504dc7eb41c--