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/06/14 15:08:00 UTC

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

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

Julian Reschke commented on OAK-8310:
-------------------------------------

trunk: (1.14.0) [r1859020|http://svn.apache.org/r1859020]
1.10: [r1861350|http://svn.apache.org/r1861350]


> 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_8
>             Fix For: 1.10.3, 1.14.0
>
>
> 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
(v7.6.3#76005)