[
https://issues.apache.org/jira/browse/OAK-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16311107#comment-16311107
]
Andrei Dulceanu commented on OAK-6373:
--------------------------------------
While working on this, it occurred to me that by adding this improvement will
make the following change to how {{oak-run check}} works: when the new option,
let's say {{--checkpoints}} will be added, then it will mean that *only the
checkpoints specified* will be checked. Without the option, the command will
work as previously, checking the {{/root}} path of the repository. I agree with
[~frm]'s suggestion of internally figuring out the paths needed to be checked
when {{--filter}} is present.
[~frm], [~mduerig], WDYT? Is this the expected outcome (i.e. having a way to
switch between checking {{/root}} or some/all checkpoints, but not both at the
same time)?
> oak-run check should also check checkpoints
> --------------------------------------------
>
> Key: OAK-6373
> URL: https://issues.apache.org/jira/browse/OAK-6373
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: run, segment-tar
> Reporter: Michael Dürig
> Assignee: Andrei Dulceanu
> Labels: tooling
> Fix For: 1.8
>
>
> {{oak-run check}} does currently *not* traverse and check the items in the
> checkpoint. I think we should change this and add an option to traverse all,
> some or none of the checkpoints. When doing this we need to keep in mind the
> interaction of this new feature with the {{filter}} option: the paths passed
> through this option need then be prefixed with {{/root}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
