[OAK-9131] oak-run tool for scanning for references to nt:frozenNode

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.34.0
• Component/s: documentmk
• Assignee: Stefan Egli
• Reporter: Stefan Egli
• Created: 02/Jul/20 13:39
• Updated: 10/Sep/20 15:45
• Resolved: 22/Jul/20 10:56

Description

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:

1. a fast scanner for nodes under /oak:index/reference
2. 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

Issue Links

• is related to: OAK-9134 Remove mix:referenceable from nt:frozenNode definition
• relates to: OAK-9139 Log message on frozen node lookup by identifier
• links to: GitHub Pull Request #238