[
https://issues.apache.org/jira/browse/OAK-7745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16612049#comment-16612049
]
Julian Reschke commented on OAK-7745:
-------------------------------------
See
https://issues.apache.org/jira/secure/attachment/12939402/OAK-7745-basic.diff -
UpdateOp with isNew==false on non-existing nodes indeed didn't have coverage in
BasicDocumentStoreTest.
The new test shows:
- MemoryDS and RDBDS throw (identical) exception (they share the same checker
method)
- MongoDS returns null and indeed creates a new document
Either we need to tune the definition of "isNew", or fix MongoDS...
> Clarify update semantics on deleted nodes
> -----------------------------------------
>
> Key: OAK-7745
> URL: https://issues.apache.org/jira/browse/OAK-7745
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: documentmk
> Reporter: Julian Reschke
> Priority: Major
> Attachments: OAK-7745-basic.diff, OAK-7745.diff
>
>
> It's not entirely clear to me what behavior we expect if:
>
> * node 1 creates a document
> * node 2 deletes it
> * node 1 tries to update it
> (and, related to that, whether the behavior really matters in practice)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
