[
https://issues.apache.org/jira/browse/OAK-8703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16956011#comment-16956011
]
Ieran Draghiciu commented on OAK-8703:
--------------------------------------
I added the documentation update in the path: [^OAK-8703-02.patch]
> Configure the maximum number of revisions to be checked by consistency check
> ----------------------------------------------------------------------------
>
> Key: OAK-8703
> URL: https://issues.apache.org/jira/browse/OAK-8703
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: oak-run, segment-tar
> Reporter: Ieran Draghiciu
> Assignee: Andrei Dulceanu
> Priority: Major
> Attachments: OAK-8703-02.patch, OAK-8703.patch
>
>
> Add the ability to configure the maximum number of request to be verify by
> the ConsistencyChecker:
> Solution:
> In *Check* builder added the *withMaxRevisionsToCheck(int
> maxRevisionsToCheck)*: Instruct the command to check only the last
> maxRevisionsToCheck
> In *CheckCommand* added the option *maxRevisionsToCheck* with default value
> 1.
> In *ConsistencyChecker* added the limitation to check only the
> @maxRevisionsToCheck:
> {code:java}
> if(maxRevisionsToCheck == revisionCount){
> break;
> }
> {code}
> *Notes:*
> if @maxRevisionsToCheck is configured 1 will check only the last revision.
> if @maxRevisionsToCheck is configured 2 will check up to 2 revisions. if the
> first revision is consistent will skip the second revision.
> ----
> Documentation changes:
> {code:java}
> The check tool inspects an existing Segment Store at PATH for eventual
> inconsistencies. The algorithm implemented by this tool traverses the last
> revision in the journal. The actual nodes and properties are traversed,
> verifying that every piece of data is reachable and undamaged. If more then 1
> revision must be verified, --maxRevisionsToCheck option can be used.
> Moreover, if --head and --checkpoints options are used, the scope of the
> traversal can be limited to head state and/or a subset of checkpoints. A deep
> scan of the content tree, traversing every node and every property will be
> performed by default. The default scope includes head state and all
> checkpoints.
> The optional --maxRevisionsToCheck [Integer] argument can be used to control
> the maximum number of revisions to be verified. Default value is 1. If the
> first revision is not consistent configure the argument to 2. This will
> verify the last 2 revisions. However if the first revision is consistent the
> verification of the second revision is skipped.
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
