jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tomek Rękawek (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-7801) CompositeNodeStore.merge() may trigger conflicting branches
Date Wed, 03 Oct 2018 12:14:00 GMT

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

Tomek Rękawek commented on OAK-7801:

I was thinking about this clause as well yesterday. I also think it was also introduced in
order to support multiple writeable repositories. We should remove the whole if() {} clause.

> 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
> 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

View raw message