[
https://issues.apache.org/jira/browse/CASSANDRA-4872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13668598#comment-13668598
]
Rick Branson commented on CASSANDRA-4872:
-----------------------------------------
Correct me if I'm wrong, but it looks like there's no longer a straightforward
way to force a re-level now (say if you changed sstable_size_in_mb). Previously
deleting the JSON manifest file would work.
> 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
> 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: http://www.atlassian.com/software/jira
