[jira] [Comment Edited] (CASSANDRA-8678) CREATE TABLE accepts value for default_time_to_live on counter table

["Jeff Jirsa (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-8678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14297460#comment-14297460 ] 

Jeff Jirsa edited comment on CASSANDRA-8678 at 1/29/15 7:59 PM:
----------------------------------------------------------------

cass-8678-3 addresses [~thobbs] style issues (boolean rather than set, consistent messaging, removed extra whitespace).

2.0 backport coming.



was (Author: jjirsa):
Addresses [~thobbs] style issues (boolean rather than set, consistent messaging, removed extra whitespace).

2.0 backport coming.


> 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
>            Assignee: Jeff Jirsa
>            Priority: Minor
>             Fix For: 2.1.2
>
>         Attachments: cass-8678-2.diff, cass-8678-3.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)