jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mete Atamel (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (OAK-351) Inconsistency issue when committing a new node under an old parent
Date Wed, 23 Jan 2013 09:54:12 GMT

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

Mete Atamel resolved OAK-351.
-----------------------------

    Resolution: Fixed

This was fixed a while back. Added the test case in rev 1437314.
                
> Inconsistency issue when committing a new node under an old parent
> ------------------------------------------------------------------
>
>                 Key: OAK-351
>                 URL: https://issues.apache.org/jira/browse/OAK-351
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: mongomk
>         Environment: all
>            Reporter: Tudor Rogoz
>         Attachments: OAK-351-automatedTest.patch
>
>
> Commit the following node structure:
> Commit 1: /a
> Commit 2: /a/b
> Commit 3: /a/b/c
> Commit 4: /a/d
> Commit will fail with the following exception:
> java.lang.RuntimeException: No such parent: a
> Note 1: 
> After the commit 3 if I run the following code
> NodeExistsCommandMongo command2 = new NodeExistsCommandMongo(
> 					mongoConnection, "/a", null);
> 			boolean exists = command2.execute();
> 			
> exist will be true, so the node is visible for NodeExistsCommandMongo class.
> Note 2:
> I created an automated test for this issue CommitCommandMongoTest.commitNodeOldParent

--
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

Mime
View raw message