[jira] [Resolved] (OAK-2246) UUID collision check is not does not work in transient space

["angela (JIRA)" <ji...@apache.org>]

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

angela resolved OAK-2246.
-------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 1.4)
                   1.2

fixed at rev. 1670603: the troublesome optimization introduced by OAK-1037 is only used if there are no transient changes pending on the importing session. also added test-cases for all import-behavior flags testing with and without transient changes pending.

if we again see performance issues with the xml import i would suggest that we perform intensive testes before rushing in any pre-mature optimization that causes regressions.

> UUID collision check is not does not work in transient space
> ------------------------------------------------------------
>
>                 Key: OAK-2246
>                 URL: https://issues.apache.org/jira/browse/OAK-2246
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: jcr
>    Affects Versions: 1.1.1
>            Reporter: Tobias Bocanegra
>            Assignee: Chetan Mehrotra
>             Fix For: 1.2
>
>
> I think OAK-1037 broke the system view import.
> test case:
> 1. create a new node with a uuid (referenceable, or new user)
> 2. import systemview with IMPORT_UUID_COLLISION_REPLACE_EXISTING
> 3. save()
> result:
> {noformat}
> javax.jcr.nodetype.ConstraintViolationException: OakConstraint0030: Uniqueness constraint violated at path [/] for one of the property in [jcr:uuid] having value e358efa4-89f5-3062-b10d-d7316b65649e
> {noformat}
> expected:
> * imported content should replace the existing node - even in transient space.
> note:
> * if you perform a save() after step 1, everything works.



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