You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2012/10/16 03:27:03 UTC
[jira] [Resolved] (CASSANDRA-4805) live update compaction strategy
destroy counter column family
[ https://issues.apache.org/jira/browse/CASSANDRA-4805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-4805.
---------------------------------------
Resolution: Invalid
Don't update CQL3 columnfamilies from the cli, it will rip out the column definitions as you see here. (1.2 prevents this, in 1.1 we are leaving it as-is.)
> live update compaction strategy destroy counter column family
> --------------------------------------------------------------
>
> Key: CASSANDRA-4805
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4805
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.5
> Environment: centos 64 , cassandra 1.1.5
> Reporter: sunjian
>
> 1. in a running cassandra cluster with 5 nodes
> 2. CLI : update column family {user_stats (a counter column family)} with compaction_strategy='LeveledCompactionStrategy'
> 3. nodetool -h host_ip compact
> result :
> can't INCR/DECR the counter column any more , but it's OK to read .
> ----------------
> counter column family definition :
> String sql = "CREATE TABLE user_stats (" +
> "user_id bigint ," +
> "counter_type text ," +
> "counter_for_what text ," +
> "counter_value counter ," +
> " PRIMARY KEY("
> + " user_id "
> + ","
> + "counter_type "
> + ","
> + "counter_for_what "
> +")) WITH read_repair_chance = 1.0 AND replicate_on_write=true " ;
> [exception]
> java.sql.SQLSyntaxErrorException: InvalidRequestException(why:Unknown identifier counter_value)
> at org.apache.cassandra.cql.jdbc.CassandraPreparedStatement.<init>(CassandraPreparedStatement.java:92)
> at org.apache.cassandra.cql.jdbc.CassandraConnection.prepareStatement(CassandraConnection.java:303)
--
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