[
https://issues.apache.org/jira/browse/CASSANDRA-4872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13575755#comment-13575755
]
Marcus Eriksson commented on CASSANDRA-4872:
--------------------------------------------
I looking at this now, i guess a requirement is to not have to do a complete
relevel on upgrade? Gets quite messy but i guess the old json-reading-code will
only have to stay for a short while though (ie, if this goes into 2.0, we can
remove the backwards-compatible code in 2.1?)
> 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: 2.0
>
>
> 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
