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?

Reply via email to