[
https://issues.apache.org/jira/browse/OAK-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13634007#comment-13634007
]
Michael Dürig commented on OAK-781:
-----------------------------------
At revision 1468890 I added another test case that demonstrates the main issue
here: Modifying node {{c}} in a hierarchy {{/a/b/c}} with {{b.exists() ==
false}} results in the original node {{c}} being overlaid by a new node {{c}}.
That new node is missing all the original items that where present on the
original version of {{c}}.
> Clarify / fix effects of MISSING_NODE as base state of NodeBuilder
> ------------------------------------------------------------------
>
> Key: OAK-781
> URL: https://issues.apache.org/jira/browse/OAK-781
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Reporter: Michael Dürig
>
> Having a {{MISSING_NODE}} respectively a node state that returns false for
> its {{exists}} method as a base state of a node builder results in undefined
> behaviour. We need to clarify how to handle such cases for resolving OAK-766.
--
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
