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 "Michael Dürig (JIRA)" <ji...@apache.org> on 2013/08/13 10:43:47 UTC

[jira] [Resolved] (OAK-947) New node becomes existing after Session.refresh(true)

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

Michael Dürig resolved OAK-947.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 0.9
         Assignee: Michael Dürig

Resolving as fixed at revision 1513388. We can address the potential performance issue together with OAK-659 by moving the new and modified logic back to the node builder.
                
> New node becomes existing after Session.refresh(true)
> -----------------------------------------------------
>
>                 Key: OAK-947
>                 URL: https://issues.apache.org/jira/browse/OAK-947
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: jcr
>    Affects Versions: 0.8
>            Reporter: Marcel Reutegger
>            Assignee: Michael Dürig
>            Priority: Minor
>             Fix For: 0.9
>
>         Attachments: OAK-947.patch
>
>
> After a session refresh(true) a new node changes it status to existing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira