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 "Tomek Rękawek (JIRA)" <ji...@apache.org> on 2017/07/20 11:50:00 UTC

[jira] [Updated] (OAK-4684) RepositorySidegrade should also run commit hooks as they are run in upgrade

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

Tomek Rękawek updated OAK-4684:
-------------------------------
    Fix Version/s: 1.0.39

> RepositorySidegrade should also run commit hooks as they are run in upgrade
> ---------------------------------------------------------------------------
>
>                 Key: OAK-4684
>                 URL: https://issues.apache.org/jira/browse/OAK-4684
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: upgrade
>            Reporter: Chetan Mehrotra
>            Assignee: Tomek Rękawek
>             Fix For: 1.4.7, 1.5.9, 1.6.0, 1.0.39
>
>
> Repository sidegrade logic currently does not execute various commit hook as required by Oak when doing partial migrations. This can leave data in inconsistent state where index data does not get updated.
> It should be ensured that all required commit hooks are run during sidegrade also.
> Note this is not a problem when whole repository is migrated via sidegrade as then relevent index path would also get copied but for partial case it would be a problem



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