[
https://issues.apache.org/jira/browse/OAK-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13486738#comment-13486738
]
Jukka Zitting commented on OAK-403:
-----------------------------------
+1 Though it would be good if the {{getIndexDefinitionNode}} code could somehow
be shared between the indexing and the lookup code.
And somewhat outside the scope of this issue, I'm not sure why the {{find()}}
method skips multi-valued properties when the else clause already handles also
that case. Same for the TODO on mvp.
> PropertyIndexLookup does not find indexes
> -----------------------------------------
>
> Key: OAK-403
> URL: https://issues.apache.org/jira/browse/OAK-403
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Affects Versions: 0.5
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Attachments: OAK-403.patch, OAK-403.patch
>
>
> The PropertyIndexLookup tries to locate the index by child node name instead
> of matching the name of the property with the values of the 'propertyNames'
> property on the index node.
> In addition the paths returned by the find() method are not absolute. This
> will result in an IllegalArgumentException when the path is turned into a
> Tree.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
