cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2735) Timestamp Based Compaction Strategy
Date Mon, 20 Jun 2011 07:39:47 GMT


Sylvain Lebresne commented on CASSANDRA-2735:

The goal here is not to have TTL for counters (or anything else). The goal is to have a compaction
strategy that as part of what it does can throw up entire sstable when the content is considered
"old enough" (and that's actually only part of the strategy, not necessarily its primary goal).
As it turns out, this will roughly (and the rough part is important) amount to expire data,
including counters. But this will be a very heavy hammer, in particular it will only work
if all the counter/data in the column family have the exact same expiration time. And this
won't work at all for say counters that you would want to start re-incrementing after expiration.
But again, this is not the goal of the ticket.

> Timestamp Based Compaction Strategy
> -----------------------------------
>                 Key: CASSANDRA-2735
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Alan Liang
>            Assignee: Alan Liang
>            Priority: Minor
>              Labels: compaction
>         Attachments: 0004-timestamp-bucketed-compaction-strategy.patch
> Compaction strategy implementation based on max timestamp ordering of the sstables while
satisfying max sstable size, min and max compaction thresholds. It also handles expiration
of sstables based on a timestamp.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message