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 2013/12/02 11:46:36 UTC

[jira] [Created] (OAK-1244) Always create new UUID on ImportBehavior.IMPORT_UUID_CREATE_NEW

Marcel Reutegger created OAK-1244:
-------------------------------------

             Summary: Always create new UUID on ImportBehavior.IMPORT_UUID_CREATE_NEW
                 Key: OAK-1244
                 URL: https://issues.apache.org/jira/browse/OAK-1244
             Project: Jackrabbit Oak
          Issue Type: Bug
          Components: jcr
    Affects Versions: 0.12
            Reporter: Marcel Reutegger
            Priority: Minor


The implementation should create a new UUID for each referenceable node even if there is no existing node with that UUID. This spec says:

bq.  Incoming nodes are assigned newly created identifiers upon addition to the workspace. As a result, identifier collisions never occur.

This will break backward compatibility, but is IMO the correct behavior and the only way to guarantee import of referenceable nodes does not fail in a concurrent import scenario. See OAK-1186 for more details.



--
This message was sent by Atlassian JIRA
(v6.1#6144)