jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-7801) CompositeNodeStore.merge() may trigger conflicting branches
Date Thu, 04 Oct 2018 08:52:00 GMT

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

Marcel Reutegger commented on OAK-7801:
---------------------------------------

Proposed changes in [^OAK-7801.patch]. Tests look good.

[~tomek.rekawek], can you please review?

> CompositeNodeStore.merge() may trigger conflicting branches
> -----------------------------------------------------------
>
>                 Key: OAK-7801
>                 URL: https://issues.apache.org/jira/browse/OAK-7801
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: composite, documentmk
>    Affects Versions: 1.9.0
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Major
>             Fix For: 1.10
>
>         Attachments: OAK-7801.patch
>
>
> This issue only affects a CompositeNodeStore with a global DocumentNodeStore. The merge()
may trigger the creation of two conflicting DocumentNodeStore branches, which then fails the
merge operation even though there is no real conflicting change. This issue does not happen
with 1.8 or earlier because those releases keep changes introduced by commit hooks in memory.
See also OAK-7401.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message