[
https://issues.apache.org/jira/browse/OAK-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13822775#comment-13822775
]
Alex Parvulescu commented on OAK-1137:
--------------------------------------
bq. making the property visible is problematic
I agree with this part, making it visible only introduces more trouble.
bq. I agree with jukka, that it would be cleaner, if the query can use the
special reference property index.
The problem here is that this 'special reference property index' doesn't exist.
We might need to tweak the query code a lot to allow for this type of mechanism
to work properly and I'm wondering if the benefits outweigh the cost.
I was considering bootstrapping in some way a property index on top of that
hidden node state, but looking at the _PropertyIndexLookup_ it also works with
_NodeState_s, so we'd still have the issue of extracting the NodeState from a
Tree.
I don't see a way forward based on queries, other than adding yet another query
index impl that would only handle references, but I'm open to more detailed
suggestions if you have them :)
bq. please don't use static imports
Thanks, but I'd much rather keep the current style, I like my code short and
sweet. We could pick this up on the dev list though.
> 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)
