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 "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2015/01/30 07:42:34 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=14298278#comment-14298278 ] 

Chetan Mehrotra commented on OAK-1550:
--------------------------------------

Probably we can special case resolution for conflicts under {{oak:index/:data}} paths as those paths are hidden and no observation events need to be generated for them. This would help in avoid performance degradation while using property indexes in a multi node deployments

> 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
>            Assignee: Marcel Reutegger
>             Fix For: 1.2
>
>
> {{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.3.4#6332)