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 2014/01/14 11:54:50 UTC

[jira] [Resolved] (OAK-1319) Skip lock check on import for new item

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

Marcel Reutegger resolved OAK-1319.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 0.15

Patch applied in http://svn.apache.org/r1558008

> Skip lock check on import for new item
> --------------------------------------
>
>                 Key: OAK-1319
>                 URL: https://issues.apache.org/jira/browse/OAK-1319
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: jcr
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Minor
>             Fix For: 0.15
>
>         Attachments: OAK-1319.patch
>
>
> Currently ImporterImpl in oak-jcr checks the lock status of the target node and throws a LockException when it is locked. To perform this check, the session is first refreshed and may cause the underlying branch to be rebased. A related issue was fixed in OAK-1294, but the rebase will still happen when there were concurrent changes.
> To further reduce the number of rebases, the Importer should only check the lock status if the node in question is not new. A new node indicates that it was possible to create the node beforehand, hence it cannot be locked.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)