[
https://issues.apache.org/jira/browse/CASSANDRA-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990201#comment-12990201
]
Kelvin Kakugawa commented on CASSANDRA-2103:
--------------------------------------------
If you look at the unit tests, it expects the above case. i.e. the last column
w/ or w/o a ttl "wins", so to speak. If two columns w/ equal timestamps are
reconciled, the non-ttl wins.
I think your above case mixes two orthogonal uses for ttls. Typically, a
column will only have ttls and they'll be updated in a fixed period w/in the
ttl, which is very useful for our case. Mixing a ttl and non-ttl use w/in the
same column is bound to produce probs. As you rightly noted.
> 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
