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 "Michael Dürig (JIRA)" <ji...@apache.org> on 2014/03/17 11:58:43 UTC
[jira] [Commented] (OAK-1550) Incorrect handling of addExistingNode
conflict in NodeStore
[ https://issues.apache.org/jira/browse/OAK-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13937660#comment-13937660 ]
Michael Dürig commented on OAK-1550:
------------------------------------
Test case at http://svn.apache.org/r1578295
> Incorrect handling of addExistingNode conflict in NodeStore
> -----------------------------------------------------------
>
> Key: OAK-1550
> URL: https://issues.apache.org/jira/browse/OAK-1550
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: mongomk
> Reporter: Michael Dürig
> Fix For: 0.20
>
>
> {{MicroKernel.rebase}} says: "addExistingNode: node has been added that is different from a node of them same name that has been added to the trunk."
> However, the {{NodeStore}} implementation
> # throws a {{CommitFailedException}} itself instead of annotating the conflict,
> # also treats the equal childs with the same name as a conflict.
--
This message was sent by Atlassian JIRA
(v6.2#6252)