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 B68732740 for ; Thu, 5 May 2011 10:19:32 +0000 (UTC) Received: (qmail 93745 invoked by uid 500); 5 May 2011 10:19:30 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 93723 invoked by uid 500); 5 May 2011 10:19:30 -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 93715 invoked by uid 99); 5 May 2011 10:19:30 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 May 2011 10:19:30 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of guofengzh@gmail.com designates 209.85.220.172 as permitted sender) Received: from [209.85.220.172] (HELO mail-vx0-f172.google.com) (209.85.220.172) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 May 2011 10:19:23 +0000 Received: by vxg33 with SMTP id 33so2560555vxg.31 for ; Thu, 05 May 2011 03:19:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=c+zsiiMiwUvjMd4atdZYF2StSwCELGAtAm7MwFU9pM8=; b=wMyteDB835gwpspPcgYpH/Fsda4050CKV+WnwHFGb4JQVUuLcetRpjCm8noeVnOriX P0fiV8A6+2zKvJLoIBSkX2Vr/1I2vK/kFm733JdFyjqNRvX1cQjzFtw33QF/n1DuV9ff K+InPMCVbYeBw2fkPIpnnT/R5CHuM1ptnSHyc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=kc0q6Q+KJLe1F5DUJ8v3RNXDSEVsbq6D68RaxFlKH3geW0Zlmdt74zCHitRi6kns+e 6vLuCXuSXwNRbXMTqT1HeG90d6xFEk1q5mrDzfPb1FfO30kYkh81qHv0MAhd5n2dJkel tsOM9Wa/XigPtFUHHtU62OTl0ZgHxU3tIxaEc= MIME-Version: 1.0 Received: by 10.52.94.170 with SMTP id dd10mr516688vdb.159.1304590741981; Thu, 05 May 2011 03:19:01 -0700 (PDT) Received: by 10.52.182.130 with HTTP; Thu, 5 May 2011 03:19:01 -0700 (PDT) Date: Thu, 5 May 2011 18:19:01 +0800 Message-ID: Subject: CQL v1.0.0: why super column family not descirbed in it? From: Guofeng Zhang To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=20cf307f31c6c0ca9204a284b36e X-Virus-Checked: Checked by ClamAV on apache.org --20cf307f31c6c0ca9204a284b36e Content-Type: text/plain; charset=ISO-8859-1 Hi, I read the CQL v1.0 document. There are operations about column families, but it does not describe how to operate on super column families. Why? Does this mean that super column families would not be supported by CQL in this version? Will it be supported in the future? Thanks. Guofeng --20cf307f31c6c0ca9204a284b36e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Hi,

=A0

I read the CQL v1.0 document. T= here are operations about column families, but it does not describe how to operate on super col= umn families. Why? Does this mean that super column families would not be suppo= rted by CQL in this version? Will it be supported in the future?

=A0

Thanks.

=A0

Guofeng

=A0

--20cf307f31c6c0ca9204a284b36e--