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 2019/05/09 14:46: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 ]
Marcel Reutegger updated OAK-8310:
----------------------------------
Summary: Potentially misleading conflict exception message (was: Potentially misleading conflict exception)
> Potentially misleading conflict exception message
> -------------------------------------------------
>
> Key: OAK-8310
> URL: https://issues.apache.org/jira/browse/OAK-8310
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: documentmk
> Affects Versions: 1.8.0, 1.10.0, 1.12.0
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Minor
>
> 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)