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 "Mete Atamel (JIRA)" <ji...@apache.org> on 2012/10/02 10:05:07 UTC
[jira] [Commented] (OAK-351) Inconsistency issue when committing a
new node under an old parent
[ https://issues.apache.org/jira/browse/OAK-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13467573#comment-13467573 ]
Mete Atamel commented on OAK-351:
---------------------------------
Test added and an initial fix implementation in my fork:
https://github.com/meteatamel/jackrabbit-oak/commit/471303a8fbd7f5ff45407424b981862cf1e2ebc7
https://github.com/meteatamel/jackrabbit-oak/commit/a2d4c8016ed6006efbbb1f3c49aac0be3dff148f
> 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: mk
> 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