cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2735) Timestamp Based Compaction Strategy
Date Wed, 02 May 2012 19:08:50 GMT


Jonathan Ellis commented on CASSANDRA-2735:

I wonder if CASSANDRA-2498 (and CASSANDRA-2503) would help here.  Since you get some help
at read time, I would imagine you wouldn't need to be so aggressive at actual compactions,
which should mitigate the extra I/O Alan mentions.
> 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: 0001-timestamp-bucketed-compaction-strategy-V2.patch, 0001-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.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message