cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-699) Add (optional) expiration time for column
Date Tue, 06 Apr 2010 16:13:33 GMT


Jonathan Ellis commented on CASSANDRA-699:

> Maybe we could then return simply the timestamp

that would make the most sense, yes.

as long as we're sure the rest of the code can handle isMarkedForDelete being true, while
the client has not yet set a deletion time (which getMarkedForDeleteAt would return).

> An expiring column could be deleted the usual way, or am I missing something ?

isMarkedForDelete only checks localExpirationTime, not a deletion explicitly set by client.

> Add (optional) expiration time for column 
> ------------------------------------------
>                 Key: CASSANDRA-699
>                 URL:
>             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, 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,
add_expiring_column_0.6beta2.diff, modify_test_0.6beta2.diff, thrift_API_change_0.6beta2.diff
> 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.

View raw message