[
https://issues.apache.org/jira/browse/CASSANDRA-4872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-4872:
---------------------------------------
Attachment:
0001-CASSANDRA-4872-move-sstable-level-into-sstable-metad-v2.patch
v2 sends back files to L0 when loadNewSSTables is called
also realized that people might drop in sstables manually and then restart
cassandra, this could make sstables within levels overlap
guess we might need to check for overlapping sstables on startup
> 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
>
>
> 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
