[
https://issues.apache.org/jira/browse/OAK-12269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18091772#comment-18091772
]
Julian Reschke commented on OAK-12269:
--------------------------------------
I would change "blocked" by "related". Both things can be implemented
separately.
> Add property to suggest index to use in AuthorizableQueryManager
> ----------------------------------------------------------------
>
> Key: OAK-12269
> URL: https://issues.apache.org/jira/browse/OAK-12269
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Reporter: Alejandro Moratinos
> Assignee: Alejandro Moratinos
> Priority: Major
>
> User/group searches built through
> org.apache.jackrabbit.api.security.user.QueryBuilder (executed via
> UserManager#findAuthorizables(Query)) are translated by UserQueryManager into
> an XPath statement. The query engine then picks an index based on cost. There
> is currently no way for a caller to influence which index is used for these
> queries.
> Oak already supports the \{{option(index tag <tag>)}} query option for
> SQL2/XPath (see [query option index
> tag|https://jackrabbit.apache.org/oak/docs/query/query-engine.html#query-option-index-tag]),
> but the user-management query API does not expose it, so it cannot be
> applied to authorizable searches.
> h4. Proposed change
> Add an index-tag hint to the user query API and propagate it into the
> generated statement.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
