[ https://issues.apache.org/jira/browse/CASSANDRA-13321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15950594#comment-15950594 ]
Marcus Eriksson commented on CASSANDRA-13321: --------------------------------------------- pushed a commit to the repo above which handles having several versions of the statistics files. On startup we find the latest version and use that. When we mutate the level/repaired info, we create a new file, and then point the sstable reader to that new file I have not written many tests for this yet, wanted to get some early feedback on the approach, wdyt [~jasobrown]? > 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)