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 2015/01/27 18:39:35 UTC

[jira] [Resolved] (OAK-2452) Avoid lookup of conflicting node with ImportUUIDBehavior.IMPORT_UUID_CREATE_NEW

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

Marcel Reutegger resolved OAK-2452.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.1.6

Done in trunk: http://svn.apache.org/r1655098

> Avoid lookup of conflicting node with ImportUUIDBehavior.IMPORT_UUID_CREATE_NEW
> -------------------------------------------------------------------------------
>
>                 Key: OAK-2452
>                 URL: https://issues.apache.org/jira/browse/OAK-2452
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: jcr
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Minor
>             Fix For: 1.1.6
>
>
> This issue is related to OAK-1244. The importer will create a new UUID for referenceable nodes when ImportUUIDBehavior.IMPORT_UUID_CREATE_NEW is used. But even with this import behavior, the importer still checks if there is a conflicting node. This is not necessary in this case and should be avoided.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)