[
https://issues.apache.org/jira/browse/OAK-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16316263#comment-16316263
]
Michael Dürig commented on OAK-6373:
------------------------------------
bq. The complicated thing in this solution is the --filter option.
I would not change anything in the semantics of {{--filter}}. That is, filter
paths are content paths. So either {{/root/foo/bar}} or
{{/checkpoints/<cp-id>/root/foo/bar}}.
bq. checkpoint is not present in the latest revision, the check ignores this
and continues checking it in the following revision and so on, until it finds a
valid version of it or there are no more revisions.
Agreed, this is exactly the behaviour I had in mind. I misread an earlier
comment and thought the suggestion was to ignore such checkpoints entirely as
if not specified on the command line.
> 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: candidate_oak_1_8, tooling
> Fix For: 1.10, 1.10.1
>
>
> {{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)
