[
https://issues.apache.org/jira/browse/OAK-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15446473#comment-15446473
]
Tomek Rękawek edited comment on OAK-4684 at 8/29/16 5:24 PM:
-------------------------------------------------------------
Updated the code - now it'll only run the commit hooks when custom
include/exclude/merge paths are defined.
Update for trunk in [r1758262|https://svn.apache.org/r1758262].
was (Author: tomek.rekawek):
Updated the code - now it'll only run the commit hooks when a custom path is
defined.
Update for trunk in [r1758262|https://svn.apache.org/r1758262].
> 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.6, 1.4.7, 1.5.9
>
>
> 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.3.4#6332)
