[
https://issues.apache.org/jira/browse/OAK-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13632865#comment-13632865
]
Jukka Zitting commented on OAK-779:
-----------------------------------
Note that we should evolve the indexing code to better leverage full node type
hierarchies so that the index would only need to be defined for
rep:Authorizable and it would automatically include also content from all
subtypes. But that's something to be addressed in a separate broader issue. See
OAK-323 and OAK-325 for some related work in different parts of the search
subsystem.
> Add rep:Authorizable to declaringNodeTypeNames of rep:principalName index
> -------------------------------------------------------------------------
>
> Key: OAK-779
> URL: https://issues.apache.org/jira/browse/OAK-779
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Minor
> Fix For: 0.7
>
>
> Currently the UserInitializer creates a rep:principalName index with two
> declaring node type names: {{rep:User}} and {{rep:Group}}.
> This allows query to make use of the index when they select the user or group
> node type, but the query engine cannot use this index when the select is for
> {{rep:Authorizable}}.
> Adding {{rep:Authorizable}} will do the trick even though it looks a bit
> strange, since {{rep:Authorizable}} is an abstract node type and you cannot
> create a node with this type. However it allows the query engine to leverage
> the index for {{rep:Authorizable}} and is correct in this case. {{rep:User}}
> and {{rep:Group}} are the only sub node types of {{rep:Authorizable}}, which
> means the index will contain all {{rep:Authorizable}}.
--
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
