[jira] [Commented] (OAK-9131) oak-run tool for scanning for references to nt:frozenNode

["Stefan Egli (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OAK-9131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17150341#comment-17150341 ] 

Stefan Egli commented on OAK-9131:
----------------------------------

* added implementation in a forked branch [here|https://github.com/stefan-egli/jackrabbit-oak/compare/trunk...stefan-egli:OAK-9131]

> oak-run tool for scanning for references to nt:frozenNode
> ---------------------------------------------------------
>
>                 Key: OAK-9131
>                 URL: https://issues.apache.org/jira/browse/OAK-9131
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: documentmk
>            Reporter: Stefan Egli
>            Assignee: Stefan Egli
>            Priority: Major
>
> As part of the effort to make nt:frozenNode no longer be a mix:referenceable there should be a tool, eg in oak-run, that allows for scanning for all potential use cases in an existing repository.
> This includes any _reference_ to an nt:frozenNode, ie actual {{Reference}} types, but potentially also {{String}} values containing a (jcr:)uuid of nt:frozenNodes.
> Such a tool can be run ad-hoc to verify if the removal of mix:referenceable from an nt:frozenNode would be problematic in a particular use case/repository.
> Two variants of this tool are currently envisioned:
> # a fast scanner for nodes under {{/oak:index/reference}}
> # a slow scanner for any node containing a uuid formatted string as any property value
> In both cases any encountered uuid is looked up and resulting node/path verified if it points to an nt:frozenNode. If that's the case, it is reported.
> The tool has 2 main outcomes:
> * exit code 0 : for success
> * exit code 1 : for the failure case where at least 1 such reference to nt:frozenNode is discovered



--
This message was sent by Atlassian Jira
(v8.3.4#803005)