jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Parvulescu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-1242) Weak reference targets added after the reference property are not indexed
Date Tue, 03 Dec 2013 18:56:35 GMT

    [ https://issues.apache.org/jira/browse/OAK-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13838033#comment-13838033

Alex Parvulescu commented on OAK-1242:

bq. fixed in r1547468

thanks, but the patch was there for feedback, I already have have commit rights so I could
have applied it myself.

> 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
> 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
> 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

This message was sent by Atlassian JIRA

View raw message