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 "Alexander Klimetschek (JIRA)" <ji...@apache.org> on 2018/10/27 02:46:00 UTC

[jira] [Resolved] (OAK-7832) oak-run console export should handle exceptions such as missing segments

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

Alexander Klimetschek resolved OAK-7832.
----------------------------------------
       Resolution: Fixed
         Assignee: Alexander Klimetschek
    Fix Version/s: 1.8.9
                   1.10

Committed to trunk in 1844932.

Backported to 1.8 in 1844933.

> oak-run console export should handle exceptions such as missing segments
> ------------------------------------------------------------------------
>
>                 Key: OAK-7832
>                 URL: https://issues.apache.org/jira/browse/OAK-7832
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: run, store-spi
>            Reporter: Alexander Klimetschek
>            Assignee: Alexander Klimetschek
>            Priority: Major
>             Fix For: 1.10, 1.8.9
>
>         Attachments: OAK-7832.patch, oak-run-1.8.9-SNAPSHOT.jar
>
>
> Problem: When trying to look at data using "pn" or running "export" oak-run console currently will choke and abort the traversal on exceptions such as SegmentNotFoundException.
> Expected: It would be nice if it would be best-effort, log the issue or embed in the exported json, and just continue. This also ensures all missing segments for a subtree are listed with one command (if it fails right now you just see the first missing segment).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)