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 "Stefan Egli (JIRA)" <ji...@apache.org> on 2015/03/10 17:56:38 UTC

[jira] [Commented] (OAK-2500) checkDeepHistory/fixDeepHistory/prepareDeepHistory for oak-mongo.js

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

Stefan Egli commented on OAK-2500:
----------------------------------

[~chetanm], would it make sense to include that in 1.0 branch? (as it affects 1.0.8 if I remember correctly)

> 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
>    Affects Versions: 1.0.8
>            Reporter: Stefan Egli
>             Fix For: 1.0.13
>
>         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)