You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2014/10/08 00:59:34 UTC

[jira] [Updated] (CASSANDRA-8078) Add a detailed compaction history table to show file lineage

     [ https://issues.apache.org/jira/browse/CASSANDRA-8078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksey Yeschenko updated CASSANDRA-8078:
-----------------------------------------
    Fix Version/s:     (was: 2.1.0)
                   2.1.1

> Add a detailed compaction history table to show file lineage
> ------------------------------------------------------------
>
>                 Key: CASSANDRA-8078
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8078
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>         Environment: Cassandra on any platform
>            Reporter: Maohua
>              Labels: features, newbie
>             Fix For: 2.1.1
>
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> Currently system.compaction_history only contains summary information about a compaction, which is useful if users only care about when the compaction occurs and the benefits generated by the compaction. However, it does not show the detailed src->dst SSTable mappings. For example, it does not show which SSTable is created or deleted as a result of compaction. As a result, when users want to backup or archive data files, they may end up backing-up different SSTables that represent exactly the same user data. 
> It will be great if there is a system.compaction_detailed_history table that remembers the detailed lineage of SSTables so the backup task does not have to figure out the duplicate data on its own.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)