Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Sat, 24 Jan 2015 17:21:34 +0000 (UTC)
From: "Aaron Ploetz (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12769876.1422120090000.165819.1422120094548@Atlassian.JIRA>
In-Reply-To: <JIRA.12769876.1422120090000@Atlassian.JIRA>
References: <JIRA.12769876.1422120090000@Atlassian.JIRA>
 <JIRA.12769876.1422120090197@arcas>
Subject: [jira] [Created] (CASSANDRA-8678) CREATE TABLE accepts value for
 default_time_to_live on counter table
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Aaron Ploetz created CASSANDRA-8678:
---------------------------------------

             Summary: 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


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)