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 "Julian Reschke (Jira)" <ji...@apache.org> on 2019/10/31 08:24:00 UTC

[jira] [Updated] (OAK-8310) Potentially misleading conflict exception message

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

Julian Reschke updated OAK-8310:
--------------------------------
    Fix Version/s: 1.4.25

> Potentially misleading conflict exception message
> -------------------------------------------------
>
>                 Key: OAK-8310
>                 URL: https://issues.apache.org/jira/browse/OAK-8310
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: documentmk
>    Affects Versions: 1.8.0, 1.10.0, 1.12.0
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Minor
>              Labels: candidate_oak_1_4
>             Fix For: 1.4.25, 1.10.3, 1.14.0, 1.6.18, 1.8.14
>
>
> A conflicting merge on a DocumentNodeStore may have a misleading exception message, when a node is added that already exists and the existing node has changes that were done after it was added.
> The conflict message will then say there's an existing node that was added at the revision it was last modified instead of when it was added.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)