[
https://issues.apache.org/jira/browse/CASSANDRA-8078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson resolved CASSANDRA-8078.
----------------------------------------
Resolution: Won't Fix
We keep track of the ancestors of files in the sstable metadata, I think that
would be enough to build what you are requesting
you can look at the data by doing tools/bin/sstablemetadata <sstable> | grep
Ancestors
> 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)
