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/13 18:04:51 UTC

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

Marcel Reutegger created OAK-1319:
-------------------------------------

             Summary: 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


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)