[
https://issues.apache.org/jira/browse/CASSANDRA-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-699:
---------------------------------------
Attachment: 0001-Add-new-ExpiringColumn-class-v2.patch
Just realize there was a bug in the previous patch introducting ExpiringColumn.
This new patch just change a intSize -> boolSize in the serialiazed size of
an ExpiringColumn.
Jaako and Kelvin: if you come up with a patch that abstract the timestamp,
I'll be happy to have a look and try to fit this patch into it.
> 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-v2.patch,
> 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.
