[
https://issues.apache.org/jira/browse/OAK-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli updated OAK-2500:
-----------------------------
Attachment: oak-mongo-mod.js
Attaching a suggested, modified version of oak-mongo.js which contains these
three new methods:
* oak.checkDeepHistory: this one goes through the entire subtree starting at a
particular path and calls oak.checkHistory on each of the nodes
* oak.prepareDeepHistory: this one is similar to checkDeepHistory, except that
the output is ready for fixing all affected nodes - ie the output consists of
"oak.fixHistory" with each affected path - which can then be executed in a
second phase to actually fix the nodes. This can be used to run against a
mongo-secondary for example - and the resulting output can be run against a
primary
* oak.fixDeepHistory: this one goes through the entire subtree starting at a
particular path and calls oak.fixHistory on each of the nodes.
> checkDeepHistory/fixDeepHistory/prepareDeepHistory for oak-mongo.js
> -------------------------------------------------------------------
>
> Key: OAK-2500
> URL: https://issues.apache.org/jira/browse/OAK-2500
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: run
> Reporter: Stefan Egli
> Attachments: oak-mongo-mod.js
>
>
> The oak-mongo.js currently contains checkHistory/fixHistory which are
> cleaning up 'dangling revisions/split-documents' on a particular path.
> Now it would be good to have a command that goes through the entire
> repository and checks/fixes these dangling revisions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
