cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-4872) Move manifest into sstable metadata
Date Tue, 19 Feb 2013 14:57:13 GMT


Jonathan Ellis updated CASSANDRA-4872:

    Tester: enigmacurry

Ryan, can you test this on a Windows VM?  Either upgrading from 1.2's LCS, or invoking the
add new sstables MBean will exercise the possibly problematic code.  (Not sure Windows will
allow us to rename over an existing file.)
> Move manifest into sstable metadata
> -----------------------------------
>                 Key: CASSANDRA-4872
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Marcus Eriksson
>            Priority: Minor
>             Fix For: 2.0
>         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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message