You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jeff Jirsa (JIRA)" <ji...@apache.org> on 2015/01/27 22:19:34 UTC
[jira] [Updated] (CASSANDRA-8678) CREATE TABLE accepts value for
default_time_to_live on counter table
[ https://issues.apache.org/jira/browse/CASSANDRA-8678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Jirsa updated CASSANDRA-8678:
----------------------------------
Attachment: cassandra-8678.diff
Prevent CREATE TABLE with default_time_to_live if counter columns are present.
> CREATE TABLE accepts value for default_time_to_live on counter table
> --------------------------------------------------------------------
>
> Key: CASSANDRA-8678
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8678
> Project: Cassandra
> Issue Type: Wish
> Components: Tools
> Reporter: Aaron Ploetz
> Priority: Minor
> Fix For: 2.1.2
>
> Attachments: cassandra-8678.diff
>
>
> I can create a counter table (via cqlsh) with a default_time_to_live:
> CREATE TABLE IF NOT EXISTS metrics2(
> time timestamp,
> value counter,
> PRIMARY KEY ((time))
> ) WITH default_time_to_live=10;
> Upsert a row that increments the counter:
> {{UPDATE metrics2 SET value=value+1 WHERE timestamp='2015-01-24 10:48 -0600';}}
> Wait 10 seconds, and select, and the row is (of course) still there. There should probably be a warning or error preventing the creation of a table that has both counter columns and a value set for default_time_to_live.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)