[
https://issues.apache.org/jira/browse/OAK-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16316131#comment-16316131
]
Michael Dürig commented on OAK-6373:
------------------------------------
IMO checking {{/root}} and all checkpoints at the same time is the most
important use case from a user's POV. As a user it is reasonable to expect that
the repository is not corrupt when {{oak-run check}} succeeds. I would thus
prefer the tool to check the head state and all checkpoints if no argument is
given. To only check the head state we could either introduce an {{head}}
option or a synthetic name {{head}} thath could be passes liked a name of a
checkpoint to the {{checkpoints}} option.
bq. If one or more of those checkpoints can't be found, the tool ignores it and
continues with the next one.
I would rather fail here to avoid the case where a user believes his repository
to be good when she miss spelled the name of a checkpoint.
> 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)
