[
https://issues.apache.org/jira/browse/OAK-8703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Dulceanu updated OAK-8703:
---------------------------------
Description:
We need the ability to configure the maximum number of revisions to be checked
by {{oak-run check}}. This way we can quickly tell whether there's a valid
revision in the last {{n}} revisions. Moreover, this comes handy when we want
to test only the last revision (current head state) of the repository.
For this we can add a new optional argument {{--maxRevisionsToCheck}}. If the
argument is used, but a specific number of revisions is not specified, the tool
will check by default only the last revision.
was:
We need the ability to configure the maximum number of revisions to be checked
by {{oak-run check}}.
For this we are adding a new argument {{--maxRevisionsToCheck}} (with default
value 1).
> 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
>
>
> We need the ability to configure the maximum number of revisions to be
> checked by {{oak-run check}}. This way we can quickly tell whether there's a
> valid revision in the last {{n}} revisions. Moreover, this comes handy when
> we want to test only the last revision (current head state) of the repository.
> For this we can add a new optional argument {{--maxRevisionsToCheck}}. If the
> argument is used, but a specific number of revisions is not specified, the
> tool will check by default only the last revision.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
