[ https://issues.apache.org/jira/browse/OAK-7224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Dulceanu updated OAK-7224: --------------------------------- Description: {{oak-run check}} does currently *not* check the checksums of the segments. As a consequence, there is no quick way of determining the state of the repository (corrupt/valid), after corrupting some random node record, as we currently do in {{CheckRepositoryTestBase#corruptRecord}}. To determine that, there needs to be an attempt to read the corrupt record as part of a traversal. An easier way would be to have a new dedicated option for this (i.e., {{--segments}}) which checks by default the content of segments against the checksums from all the tar files in the specified location. Additionally, it could accept as an argument a list of tar files, the segments of which to be checked. was: {{oak-run check}} does currently *not* check the checksums of the segments. As a consequence, there is no quick way of determining the state of the repository (corrupt/valid), after corrupting some random node record, as we currently do in {{CheckRepositoryTestBase#corruptRecord}}. To determine that, there needs to be an attempt to read the corrupt record as part of a traversal. An easier way would be to have a new dedicated option for this (i.e., {{--segments}}) which checks by default all segments from all the tar files in the specified location. Additionally, it could accept as an argument a list of tar files, the segments of which to be checked. > oak-run check should have an option to check the segments checksums > ------------------------------------------------------------------- > > Key: OAK-7224 > URL: https://issues.apache.org/jira/browse/OAK-7224 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: run, segment-tar > Reporter: Andrei Dulceanu > Assignee: Andrei Dulceanu > Priority: Minor > Labels: tooling > Fix For: 1.9.0, 1.10 > > > {{oak-run check}} does currently *not* check the checksums of the segments. > As a consequence, there is no quick way of determining the state of the > repository (corrupt/valid), after corrupting some random node record, as we > currently do in {{CheckRepositoryTestBase#corruptRecord}}. To determine that, > there needs to be an attempt to read the corrupt record as part of a > traversal. > An easier way would be to have a new dedicated option for this (i.e., > {{--segments}}) which checks by default the content of segments against the > checksums from all the tar files in the specified location. Additionally, it > could accept as an argument a list of tar files, the segments of which to be > checked. -- This message was sent by Atlassian JIRA (v7.6.3#76005)