[
https://issues.apache.org/jira/browse/OAK-7832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16654436#comment-16654436
]
Alexander Klimetschek commented on OAK-7832:
--------------------------------------------
Fixed the license header (my IDE should have a smart copyright profile
detection :D).
I could commit myself.
This change was done against the 1.8 branch, but it patches without changes
against trunk. Given many production users (for which oak-run is useful) are on
1.8, should I commit to both?
> 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
> Priority: Major
> 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)
