cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nikolay (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2103) expiring counter columns
Date Tue, 05 Feb 2013 14:39:13 GMT


Nikolay commented on CASSANDRA-2103:

What about following use case:

First time when you increase the counter (e.g. counter does not exists), you supply TTL.
Then counter is created with this TTL.

Next, the TTL is ignored, until counter is "alive".

This means if you create it with TTL 1 week, counter will be "alive" for a week, then it expires
and then it is created again , and assuming you still give TTL 1 week, counter is like resetting.

In this case implementation will not be that hard I believe, since all replicas will have
consolidated expire date?
> expiring counter columns
> ------------------------
>                 Key: CASSANDRA-2103
>                 URL:
>             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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message