[
https://issues.apache.org/jira/browse/CASSANDRA-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990651#comment-12990651
]
Kelvin Kakugawa commented on CASSANDRA-2103:
--------------------------------------------
Yes, I agree w/ you.
Our use case is very narrow. We basically want fine-grained deletes, w/o
having to periodically sweep the data store for irrelevant keys. We're not
interested in reading the data when it's at the end of the ttl bound.
A non-ideal solution to the above situation would be to never extend
localExpirationTime, once its been set. It would still work for our case, but
it would lose flexibility. i.e. if you make a mistake, you can't fix it.
> 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
> Reporter: Kelvin Kakugawa
> Assignee: Kelvin Kakugawa
> Fix For: 0.8
>
> Attachments: 0001-CASSANDRA-2103-expiring-counters-logic-tests.patch
>
>
> add ttl functionality to counter columns.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
