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 "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2018/10/03 10:01:00 UTC

[jira] [Created] (OAK-7801) CompositeNodeStore.merge() may trigger conflicting branches

Marcel Reutegger created OAK-7801:
-------------------------------------

             Summary: 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
             Fix For: 1.10


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)