cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan McGuire (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-4872) Move manifest into sstable metadata
Date Fri, 02 May 2014 16:16:20 GMT

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

Ryan McGuire updated CASSANDRA-4872:
------------------------------------

    Labels: qa-resolved  (was: )

> Move manifest into sstable metadata
> -----------------------------------
>
>                 Key: CASSANDRA-4872
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4872
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Marcus Eriksson
>            Priority: Minor
>              Labels: 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.2#6252)

Mime
View raw message