[
https://issues.apache.org/jira/browse/CASSANDRA-4872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13486124#comment-13486124
]
Sylvain Lebresne commented on CASSANDRA-4872:
---------------------------------------------
bq. With information per-sstable we don't need to do a full re-level if there
is corruption.
I'm not completely sure what you mean by that? Even if we do that ticket, we
will need to reconstruct the manifest in-memory, and in doing that we might get
corruption as well.
I'm not saying I'm completely opposed to the idea, but I'm not I understand the
benefits and it does seem to introduce some complexity (you'd have to
reconstruct the manifest info from spread out sources).
> 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
> Priority: Minor
> Fix For: 1.3
>
>
> 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: http://www.atlassian.com/software/jira
