Description
The implementation should create a new UUID for each referenceable node even if there is no existing node with that UUID. This spec says:
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.
Attachments
Issue Links
- blocks
-
OAK-1186 Parallel execution of ConcurrentReadAccessControlledTreeTest fails with MongoMK
-
- Closed
-
- is related to
-
OAK-2452 Avoid lookup of conflicting node with ImportUUIDBehavior.IMPORT_UUID_CREATE_NEW
-
- Closed
-
- relates to
-
JCRVLT-763 IdConflictPolicy: improve documentation for CREATE_NEW_ID
-
- Closed
-