[
https://issues.apache.org/jira/browse/OAK-5621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15861086#comment-15861086
]
Thomas Mueller commented on OAK-5621:
-------------------------------------
http://svn.apache.org/r1782447 (trunk)
* Added tests
* Move the verification logic away from the "prepare" phase into a separate
method
* For both joins and SQL-2 queries using "or", verification is only needed if
_all_ possible path use traversal
> Warn traversal queries: false positives for joins and SQL-2 queries using "or"
> ------------------------------------------------------------------------------
>
> Key: OAK-5621
> URL: https://issues.apache.org/jira/browse/OAK-5621
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: query
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Fix For: 1.8, 1.6.1
>
>
> The following query logs that the query doesn't use an index:
> {noformat}
> /jcr:root/content//*/jcr:content[@jcr:uuid =
> '03b6fd98-e5f1-4674-9bce-d02c9b17cecd']
> {noformat}
> The query correctly uses the uuid index to locate the node, and then
> traverses the parent nodes to verify the path constraint matches. So,
> strictly speaking this is traversal, but only traversal to the parent nodes,
> and not traversal down the tree. Traversal to the parent nodes is not
> problematic, so no message should be logged.
> A workaround it to change the query by appending {{option(traversal ok)}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
