[
https://issues.apache.org/jira/browse/CASSANDRA-13321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905186#comment-15905186
]
Marcus Eriksson commented on CASSANDRA-13321:
---------------------------------------------
good points, fixed the tests and the method rename in my last commit
And I agree that we need to do something about the double renaming - will work
on this. My plan now is to add a "version" number to the sstable metadata file,
then we can atomically switch which file we are using and remove the old files
after that. And if they are still on disk, no problem, we only use the latest
version.
> Add a checksum component for the sstable metadata (-Statistics.db) file
> -----------------------------------------------------------------------
>
> Key: CASSANDRA-13321
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13321
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Fix For: 4.x
>
>
> Since we keep important information in the sstable metadata file now, we
> should add a checksum component for it. One danger being if a bit gets
> flipped in repairedAt we could consider the sstable repaired when it is not.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
