[
https://issues.apache.org/jira/browse/OAK-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13822710#comment-13822710
]
Tobias Bocanegra commented on OAK-1137:
---------------------------------------
making the property visible is problematic in respect to access control. for
example if the session does not have read access to one of the source nodes.
I agree with jukka, that it would be cleaner, if the query can use the special
reference property index. this also has the advantage that for rare cases,
where a user query includes such clauses will be faster.
*sidenote*: please don't use static imports - or at least not for methods. they
make the code rather difficult to read, especially outside a IDE.
{code}
- return PathUtils.concat(parentId, tree.getName());
+ return concat(parentId, tree.getName());
{code}
> Node.getReferences() is slow due to missing property index
> ----------------------------------------------------------
>
> Key: OAK-1137
> URL: https://issues.apache.org/jira/browse/OAK-1137
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, jcr
> Affects Versions: 0.10
> Reporter: Tobias Bocanegra
> Assignee: Alex Parvulescu
> Priority: Critical
> Fix For: 0.12
>
> Attachments: OAK-1137.patch
>
>
> Node.getReferences() traverses all items in the repository in order to find
> the properties that reference the given node. this is super slow and does not
> scale.
> the (weak) reference properties should be auto-indexed.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
