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 "Tobias Bocanegra (JIRA)" <ji...@apache.org> on 2013/12/03 17:42:50 UTC

[jira] [Resolved] (OAK-1242) Weak reference targets added after the reference property are not indexed

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

Tobias Bocanegra resolved OAK-1242.
-----------------------------------

    Resolution: Fixed

fixed in r1547468

> Weak reference targets added after the reference property are not indexed
> -------------------------------------------------------------------------
>
>                 Key: OAK-1242
>                 URL: https://issues.apache.org/jira/browse/OAK-1242
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>    Affects Versions: 0.12
>            Reporter: Tobias Bocanegra
>            Priority: Blocker
>             Fix For: 0.13
>
>         Attachments: OAK-1242.patch
>
>
> with the introduction of a special index for (weak)references by OAK-1137, they are only indexed if a reference property is written, but not if a weak reference target is added later on.
> see {{org.apache.jackrabbit.oak.jcr.ReferencesTest#testWeakReferencesAddLater}} that fails currently.
> the only workaround is to re-set the weak reference property after adding the referenceable node. 
> looking at this regression, I don't think that the current approach of storing the back references is a good one as it does not work for this case. IMO a separate index of all reference properties, grouped by UUID of the target referenceable needs to be kept outside of the normal tree.



--
This message was sent by Atlassian JIRA
(v6.1#6144)