[
https://issues.apache.org/jira/browse/CASSANDRA-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802464#action_12802464
]
Kelvin Kakugawa commented on CASSANDRA-699:
-------------------------------------------
Jaakko and I are working through a couple strategies, right now. Sub-classing
vs. a new Clock class to encapsulate "priority".
At the moment, we have a working (but, not completely tested) patch that
sub-classes Column/SuperColumn. However, timestamp/version really just
encompasses one concept: priority. So, we're trying to see if we can come up
w/ a more concise patch that just abstracts out timestamp.
> Add (optional) expiration time for column
> ------------------------------------------
>
> Key: CASSANDRA-699
> URL: https://issues.apache.org/jira/browse/CASSANDRA-699
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Fix For: 0.7
>
> Attachments: 0001-Add-new-ExpiringColumn-class.patch,
> 0002-Add-TTL-support-to-cassandra.thrift.patch,
> 0003-Plug-thrift-TTL-addition-to-ExpiringColumn.patch,
> 0004-Update-test_server-for-insert-changes-and-add-simple.patch
>
>
> Allow to attach an expiration time to a column.
> An expired column would act much like a 'markedForDelete' one.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
