[
https://issues.apache.org/jira/browse/CASSANDRA-6370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne reopened CASSANDRA-6370:
-----------------------------------------
Assignee: Sylvain Lebresne
I'm going to reopen because while I agree that you should absolutely stick to
cqlsh when dealing with CQL3 tables, I think it doesn't cost us much to either
make sure it's not too easy to shoot yourself in the foot or at least disallow
modifications of CQL3 table from thrift if that screw them up (especially since
it's pretty damn hard to get back on your feet afterwards unless you're very
familiar with the schema code).
> Updating cql created table through cassandra-cli transform it into a compact
> storage table
> ------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-6370
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6370
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Alain RODRIGUEZ
> Assignee: Sylvain Lebresne
> Priority: Critical
>
> To reproduce :
> echo "CREATE TABLE test (aid int, period text, event text, viewer text,
> PRIMARY KEY (aid, period, event, viewer) );" | cqlsh -kmykeyspace;
> echo "describe table test;" | cqlsh -kmykeyspace;
> Output >
> CREATE TABLE test (
> aid int,
> period text,
> event text,
> viewer text,
> PRIMARY KEY (aid, period, event, viewer)
> ) 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
> 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': 'SnappyCompressor'};
> Then do :
> echo "update column family test with dclocal_read_repair_chance = 0.1;" |
> cassandra-cli -kmykeyspace
> And finally again : echo "describe table test;" | cqlsh -kmykeyspace;
> Output >
> CREATE TABLE test (
> aid int,
> column1 text,
> column2 text,
> column3 text,
> column4 text,
> value blob,
> PRIMARY KEY (aid, column1, column2, column3, column4)
> ) WITH COMPACT STORAGE AND
> bloom_filter_fp_chance=0.010000 AND
> caching='KEYS_ONLY' AND
> comment='' AND
> dclocal_read_repair_chance=0.100000 AND
> gc_grace_seconds=864000 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': 'SnappyCompressor'};
> This is quite annoying in production. If it is happening to you:
> UPDATE system.schema_columnfamilies SET column_aliases =
> '["period","event","viewer"]' WHERE keyspace_name='mykeyspace' AND
> columnfamily_name='test'; should help restoring the table. (Thanks Sylvain
> for this information.)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
