jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Updated] (OAK-1553) More sophisticated conflict resolution when concurrently adding nodes
Date Thu, 22 Dec 2016 14:36:58 GMT

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

Michael Dürig updated OAK-1553:
    Labels: concurrency scalability technical_debt  (was: concurrency technical_debt)

> More sophisticated conflict resolution when concurrently adding nodes
> ---------------------------------------------------------------------
>                 Key: OAK-1553
>                 URL: https://issues.apache.org/jira/browse/OAK-1553
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, mongomk, segment-tar
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>              Labels: concurrency, scalability, technical_debt
>         Attachments: OAK-1553.patch
> {{MicroKernel.rebase}} currently specifies: "addExistingNode: A node has been added that
is different from a node of them same name that has been added to the trunk."
> This is somewhat troublesome in the case where the same node with different but non conflicting
child items is added concurrently:
> {code}
> f.add("fo").add("u1"); commit();
> f.add("fo").add("u2"); commit();
> {code}
> currently fails with a conflict because {{fo}} is not the same node for the both cases.
See discussion http://markmail.org/message/flst4eiqvbp4gi3z

This message was sent by Atlassian JIRA

View raw message