You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Wei Deng (JIRA)" <ji...@apache.org> on 2016/07/21 05:42:20 UTC
[jira] [Updated] (CASSANDRA-4872) Move manifest into sstable
metadata
[ https://issues.apache.org/jira/browse/CASSANDRA-4872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wei Deng updated CASSANDRA-4872:
--------------------------------
Labels: lcs qa-resolved (was: qa-resolved)
> Move manifest into sstable metadata
> -----------------------------------
>
> Key: CASSANDRA-4872
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4872
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jonathan Ellis
> Assignee: Marcus Eriksson
> Priority: Minor
> Labels: lcs, qa-resolved
> Fix For: 2.0 beta 1
>
> Attachments: 0001-CASSANDRA-4872-move-sstable-level-into-sstable-metad-v1.patch, 0001-CASSANDRA-4872-move-sstable-level-into-sstable-metad-v2.patch, 0001-CASSANDRA-4872-move-sstable-level-into-sstable-metad-v3.patch, 0001-CASSANDRA-4872-move-sstable-level-into-sstable-metad-v4.patch, 0001-CASSANDRA-4872-wip-v6.patch, 0001-CASSANDRA-4872-wip-v7.patch, 4872-v5.txt
>
>
> Now that we have a metadata component it would be better to keep sstable level there, than in a separate manifest. With information per-sstable we don't need to do a full re-level if there is corruption.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)