[
https://issues.apache.org/jira/browse/OAK-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313198#comment-16313198
]
Francesco Mari commented on OAK-6373:
-------------------------------------
I think the command should behave in the following way.
* The path passed to {{filter}} should always be a content path, i.e. no
super-root or checkpoint prefix should be specified by the user.
* If {{checkpoints}} is not specified, the command checks the head state.
* If {{checkpoints}} is specified, the command checks the checkpoints but not
the head state.
* If no arguments are specified for {{checkpoints}}, every checkpoint is
checked.
* If one or more arguments are specified for {{checkpoints}}, they are the
checkpoints that should be checked. If one or more of those checkpoints can't
be found, the tool ignores it and continues with the next one.
The only use case that the points above don't cover is checking the head state
and the checkpoints with one invocation. Either we ignore this use case, or we
add an additional {{head}} option that, when used in combination with
{{checkpoints}}, allows the traversal of both the head state and the specified
checkpoints. {{head}} doesn't have any effect unless {{checkpoints}} is
specified. This might be tackled by a future improvement.
> 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)
