You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Alan Liang (JIRA)" <ji...@apache.org> on 2011/06/09 22:02:58 UTC
[jira] [Issue Comment Edited] (CASSANDRA-2735) Timestamp Based
Compaction Strategy
[ https://issues.apache.org/jira/browse/CASSANDRA-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046750#comment-13046750 ]
Alan Liang edited comment on CASSANDRA-2735 at 6/9/11 8:01 PM:
---------------------------------------------------------------
Splitting out the capturing of max client supplied timestamp into a separate ticket (#2753) so that other tickets can benefit.
was (Author: alanliang):
Splitting out the capturing of max client supplied timestamp into a separate ticket so that other tickets can benefit.
> Timestamp Based Compaction Strategy
> -----------------------------------
>
> Key: CASSANDRA-2735
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2735
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Alan Liang
> Assignee: Alan Liang
> Priority: Minor
> Labels: compaction
> Attachments: 0002-timestamp-bucketed-compaction-strategy.patch, 0003-implemented-timestamp-bucketed-compaction-strategy-a.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: http://www.atlassian.com/software/jira