cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-4872) Move manifest into sstable metadata
Date Sat, 16 Feb 2013 21:49:13 GMT


Marcus Eriksson updated CASSANDRA-4872:

    Attachment: 0001-CASSANDRA-4872-wip-v6.patch

* Removes the max(..) in SSTM
* Moves the overlapping check to LeveledManifest.create(..) - this also makes sure that we
are in a good state when people change compaction strategy to LCS
* add license header to LegacyLeveledManifest

btw, git show doesn't include the binary files, git format-patch does
> 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,
> 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