cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-5228) Track maximum ttl and use to expire entire sstables
Date Wed, 06 Mar 2013 09:40:13 GMT


Marcus Eriksson updated CASSANDRA-5228:

    Attachment: 0001-track-max-ttl-v1.patch

first attempt at a first part that just tracks max ttl on sstables, figured this ticket could
be split in 2 patches

next part will drop sstables after maxTimestamp + maxTTL + gc_grace_seconds - we need to take
gc_grace in account here since deletes don't have a ttl, meaning we could drop tombstones
too early. (another approach might be to say that DeletedColumn TTL is gc_grace_seconds?)
> Track maximum ttl and use to expire entire sstables
> ---------------------------------------------------
>                 Key: CASSANDRA-5228
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jonathan Ellis
>            Priority: Minor
>         Attachments: 0001-track-max-ttl-v1.patch
> It would be nice to be able to throw away entire sstables worth of data when we know
that it's all expired.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message