Ryan McGuire created CASSANDRA-5749:
---------------------------------------
Summary: DESC TABLE omits some column family settings
Key: CASSANDRA-5749
URL: https://issues.apache.org/jira/browse/CASSANDRA-5749
Project: Cassandra
Issue Type: Bug
Affects Versions: 2.0 beta 1, 2.0
Reporter: Ryan McGuire
Priority: Minor
In CQL I can create a table with settings introduced in 2.0:
{code}
cqlsh:Keyspace1> CREATE TABLE r1 ( key int PRIMARY KEY, value varchar) WITH
speculative_retry='ALWAYS';
{code}
But the settings don't show up when I DESC TABLE:
{code}
cqlsh:Keyspace1> DESC TABLE r1;
CREATE TABLE r1 (
key int PRIMARY KEY,
value text
) WITH
bloom_filter_fp_chance=0.010000 AND
caching='KEYS_ONLY' AND
comment='' AND
dclocal_read_repair_chance=0.000000 AND
gc_grace_seconds=864000 AND
index_interval=128 AND
read_repair_chance=0.100000 AND
replicate_on_write='true' AND
populate_io_cache_on_flush='false' AND
compaction={'class': 'SizeTieredCompactionStrategy'} AND
compression={'sstable_compression': 'LZ4Compressor'};
{code}
For comparison, here is the same table viewed from cassandra-cli:
{code}
[default@Keyspace1] describe r1;
WARNING: CQL3 tables are intentionally omitted from 'describe' output.
See https://issues.apache.org/jira/browse/CASSANDRA-4377 for details.
WARNING: Could not connect to the JMX on 127.0.0.1:7199 - some information
won't be shown.
ColumnFamily: r1
Key Validation Class: org.apache.cassandra.db.marshal.Int32Type
Default column value validator: org.apache.cassandra.db.marshal.BytesType
Cells sorted by:
org.apache.cassandra.db.marshal.CompositeType(org.apache.cassandra.db.marshal.UTF8Type)
GC grace seconds: 0
Compaction min/max thresholds: 0/0
Read repair chance: 0.0
DC Local Read repair chance: 0.0
Populate IO Cache on flush: false
Replicate on write: false
Caching: keys_only
Default time to live: 0
Bloom Filter FP chance: default
Index interval: default
Speculative Retry: NONE
Compaction Strategy: null
{code}
Ideally, all of these values that cli shows would be shown by cqlsh.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira