You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Marco Palladino (JIRA)" <ji...@apache.org> on 2015/02/02 23:19:38 UTC

[jira] [Comment Edited] (CASSANDRA-2103) expiring counter columns

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

Marco Palladino edited comment on CASSANDRA-2103 at 2/2/15 10:19 PM:
---------------------------------------------------------------------

I do also agree with Nikolay and Amol. My use case is about storing analytics information and then deleting data when it gets too old and the counters are not incremented/used by the application anymore. 

I am no expert, but maybe another option would be complying with the TTL set when creating the table using {{default_time_to_live}} (as opposed as setting the TTL when increasing the counter for the first time, which is also a nice option to have). The application itself could then control the rotation of data by storing/duplicating counters in "hot" or "frozen" tables. This would require some more planning when creating the data model, as such it would be totally fine to only allow the TTL when creating the table the first time, and prevent the TTL from being set when altering the table.


was (Author: thefosk):
I do also agree with Nikolay and Amol. My use case is about storing analytics information and then deleting data when they get too old and are not incremented/used by the application anymore. 

I am no expert, but maybe another option would be complying with the TTL set when creating the table using {{default_time_to_live}} (as opposed as setting the TTL when increasing the counter for the first time, which is also a nice option to have). The application itself could then control the rotation of data by storing/duplicating counters in "hot" or "frozen" tables. This would require some more planning when creating the data model, as such it would be totally fine to only allow the TTL when creating the table the first time, and prevent the TTL from being set when altering the table.

> expiring counter columns
> ------------------------
>
>                 Key: CASSANDRA-2103
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2103
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 0.8 beta 1
>            Reporter: Kelvin Kakugawa
>         Attachments: 0001-CASSANDRA-2103-expiring-counters-logic-tests.patch
>
>
> add ttl functionality to counter columns.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)