[
https://issues.apache.org/jira/browse/OAK-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13823789#comment-13823789
]
Alex Parvulescu commented on OAK-685:
-------------------------------------
Thanks for the input [~tripod], please see the patch on OAK-1137 for an updated
storage structure, which also passes this test.
As for the test itself, I think it's an unfair setup, this problem appears in
any 'concurrent update on the same MVP' situation. This is what happened with
the property index a while back too. It goes deeper into the MK impl (each
existing mk handles this differently), and it's not really tied to the
reference bits.
This being said, you can see the patch solves this problem too, so this is no
longer an issue.
> Enforce referential integrity for referenceable nodes
> -----------------------------------------------------
>
> Key: OAK-685
> URL: https://issues.apache.org/jira/browse/OAK-685
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: core, jcr
> Reporter: Michael Dürig
> Assignee: Alex Parvulescu
> Priority: Critical
> Fix For: 0.11
>
> Attachments: ConcurrentAddReferenceTest.java.patch, OAK-685-v2.patch,
> OAK-685.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.1#6144)
