[
https://issues.apache.org/jira/browse/OAK-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13825419#comment-13825419
]
Alex Parvulescu commented on OAK-1137:
--------------------------------------
thanks Michael for the feedback!
bq. As mentioned I'd prefer not using queries for resolving UUIDs as finding
the respective properties from the nodes returned by the query is fiddly, but I
can also live with this.
The biggest problem with not using a query is how to extract the NodeState from
the Tree. It does look like bootstrapping a lite query engine (just the lookup
parts really) is in the end cheaper, but all query related bits work on
NodeStates.
> 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-v2.patch, OAK-1137-v3.patch, 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)
