You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Shivam (Jira)" <ji...@apache.org> on 2026/10/12 11:09:00 UTC

[jira] [Updated] (OAK-12455) Oak-run check: add --continue-on-error to report all inconsistent paths in one run

     [ https://issues.apache.org/jira/browse/OAK-12455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shivam updated OAK-12455:
-------------------------
    Description: 
*oak-run* check stops traversing a tree at the first inconsistency it finds.

Add an opt-in option, *--continue-on-error.* With it, the traversal keeps going after an inconsistency and reports every inconsistent node it can reach, using the existing _Error while traversing <path>_ messages. The result is unchanged: the command still prints *No good revision found* and exits with 1 if anything is inconsistent.

Without the option, behaviour is unchanged. 

  was:
*oak-run* check stops traversing a tree at the first inconsistency it finds.

Add an opt-in option, *--continue-on-error.* With it, the traversal keeps going after an inconsistency and reports every inconsistent node it can reach, using the existing _Error while traversing <path>_ messages. The result is unchanged: the command still prints *No good revision found* and exits with 1 if anything is inconsistent.

Without the option, behaviour is unchanged. It is intended for use as *check <store> --head --last 1 --continue-on-error.*


> Oak-run check: add --continue-on-error to report all inconsistent paths in one run
> ----------------------------------------------------------------------------------
>
>                 Key: OAK-12455
>                 URL: https://issues.apache.org/jira/browse/OAK-12455
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: oak-run
>    Affects Versions: 2.6.0
>            Reporter: Shivam
>            Priority: Minor
>
> *oak-run* check stops traversing a tree at the first inconsistency it finds.
> Add an opt-in option, *--continue-on-error.* With it, the traversal keeps going after an inconsistency and reports every inconsistent node it can reach, using the existing _Error while traversing <path>_ messages. The result is unchanged: the command still prints *No good revision found* and exits with 1 if anything is inconsistent.
> Without the option, behaviour is unchanged. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)