You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2017/02/21 18:37:44 UTC

[jira] [Resolved] (OAK-5743) UserQueryManager: omits nt-name when searching for properties without path deliminator

     [ https://issues.apache.org/jira/browse/OAK-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

angela resolved OAK-5743.
-------------------------
    Resolution: Fixed

Committed revision 1783916.


> UserQueryManager: omits nt-name when searching for properties without path deliminator
> --------------------------------------------------------------------------------------
>
>                 Key: OAK-5743
>                 URL: https://issues.apache.org/jira/browse/OAK-5743
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: angela
>            Assignee: angela
>             Fix For: 1.7.0, 1.8
>
>
> The query generated for {{UserManager.findAuthorizables(String relPath, String value, int searchType)}} and {{UserManager.findAuthorizables(String relPath, String value)}} doesn't include the node type name in the query statement if the {{relPath}} param doesn't include a path deliminator.
> While the contract mandates that a simple {{propertyName}} will result in a query that search the whole subtree defined by a given authorizable (i.e. including properties defined at child nodes) this causes a traversal query even for properties like {{rep:principalName}} or {{rep:authorizableId}}, which are considered reserved and are covered with a dedicated index. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)