Return-Path: 
 <user-return-30122-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 24059D1DC
	for <apmail-cassandra-user-archive@www.apache.org>;
 Wed, 14 Nov 2012 13:20:21 +0000 (UTC)
Received: (qmail 73236 invoked by uid 500); 14 Nov 2012 13:20:20 -0000
Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org
Received: (qmail 72024 invoked by uid 500); 14 Nov 2012 13:20:13 -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 71890 invoked by uid 99); 14 Nov 2012 13:20:11 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Nov 2012 13:20:11 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,HTML_OBFUSCATE_05_10,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of timm.turn@gmail.com
 designates 209.85.219.44 as permitted sender)
Received: from [209.85.219.44] (HELO mail-oa0-f44.google.com) (209.85.219.44)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Nov 2012 13:20:05 +0000
Received: by mail-oa0-f44.google.com with SMTP id n5so423265oag.31
        for <user@cassandra.apache.org>; Wed, 14 Nov 2012 05:19:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=kAGMm8tcQRGROZghuMBuG+NFUjawIeiOGVKebEK88xI=;
        b=LtEmB3oUdgTvwfXvbVO0cM4Bg+HcEk75xxUjCLd/i3A2DoNMHyLJOlVC+4VoC5GzhF
         YfWJbm5nhJjkkxtfnEx5jSyAzqNb+HXm6Cev3WJIXn5Vzf1rdzBndbXSHVlTTT+pcORO
         /1DpOapHkYLkN+TFLiEOaOp/TRJuyD9tb5K02RX5vZkgcLgDLe6Mc4AR41zHFbsJdDjm
         iHLafrvWmQoVcNJ+GP2GMnfq2U4MGzy8iNcNulXBTg8ZgQeOIdd98RlBjoaRp3Ioj2y8
         JvRaqf1i+Zpx7hOEsQjWXyNp/LqAP1TfR1Hx5zzv5b+Po9Q7RLqo5VslBsEtXfPNRRjn
         mbjg==
MIME-Version: 1.0
Received: by 10.60.169.243 with SMTP id ah19mr20142867oec.127.1352899184399;
 Wed, 14 Nov 2012 05:19:44 -0800 (PST)
Received: by 10.60.171.40 with HTTP; Wed, 14 Nov 2012 05:19:44 -0800 (PST)
Date: Wed, 14 Nov 2012 14:19:44 +0100
Message-ID: 
 <CA+uKMZCZa6f1-QuoxXoG=7Jw1Nygsmejk2dL_EtniTJ1zoRgzQ@mail.gmail.com>
Subject: describe columnfamilies?
From: Timmy Turner <timm.turn@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=bcaec517a6b44d972504ce74636a
X-Virus-Checked: Checked by ClamAV on apache.org

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

Using a describe columnfamilies/tables query, Cassandra only gives me
<empty> in 1.2.0-beta1 and the error mentioned in
https://issues.apache.org/jira/browse/CASSANDRA-4946 in 1.2.0-beta2,
despite there actually being columnfamilies in the currently selected/used
keyspace. Selecting/updating the columnfamilies and describe columnfamily
statements work fine.

Is this a bug that will eventually be fixed, or does describe
columnfamilies only list the columnfamilies after certain conditions (e.g.
only after they've been flushed to the disk) have been met? If so, what are
these conditions, and is there any way to force Cassandra to execute the
necessary steps to meet these conditions?

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

Using a describe columnfamilies/tables query, Cassandra only gives me &lt;e=
mpty&gt; in 1.2.0-beta1 and the error mentioned in=A0
<a href=3D"https://issues.apache.org/jira/browse/CASSANDRA-4946">https://is=
sues.apache.org/jira/browse/CASSANDRA-4946</a>=A0in 1.2.0-beta2, despite th=
ere actually being columnfamilies in the currently selected/used keyspace.=
=A0Selecting/updating the columnfamilies and describe columnfamily statemen=
ts work fine.<div>
<br></div><div>Is this a bug that will eventually be fixed, or does describ=
e columnfamilies only list the columnfamilies after certain conditions (e.g=
. only after they&#39;ve been flushed to the disk) have been met? If so, wh=
at are these conditions, and is there any way to force Cassandra to execute=
 the necessary steps to meet these conditions?<br>
<div><div><br></div></div></div>

--bcaec517a6b44d972504ce74636a--