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 "Michael Dürig (JIRA)" <ji...@apache.org> on 2017/06/20 07:51:00 UTC

[jira] [Updated] (OAK-6371) Implement better tools for reparing a corrupt repository

     [ https://issues.apache.org/jira/browse/OAK-6371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Dürig updated OAK-6371:
-------------------------------
    Labels: tooling  (was: )

> Implement better tools for reparing a corrupt repository 
> ---------------------------------------------------------
>
>                 Key: OAK-6371
>                 URL: https://issues.apache.org/jira/browse/OAK-6371
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: core, segment-tar
>            Reporter: Michael Dürig
>              Labels: tooling
>             Fix For: 1.7.6
>
>
> In a recent customer case we had the requirement to remove corrupted nodes from a repository (instead of rolling it back via {{oak-run check}} and subsequently editing the {{journal.log}}. The current ad-hoc way of doing so is via the [rmNode|https://gist.githubusercontent.com/stillalex/43c49af065e3dd1fd5bf/raw/9e726a59f75b46e7b474f7ac763b0888d5a3f0c3/rmNode.groovy] Groovy script. Since in that case the corrupted nodes where inside a checkpoint we couldn't use this approach though. 
> Going forward we should implement more robust tooling around this use case:
> * Remove corrupt nodes and properties and log their path
> * Copy the repository (head state) to a new repository skipping all corrupt nodes and properties while logging their path. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)