[
https://issues.apache.org/jira/browse/SLING-6506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15851998#comment-15851998
]
David Gonzalez commented on SLING-6506:
---------------------------------------
The query executed prior to this is executed as a UNION by oak and the
incorrect plan called out above appears to match the latter query in the Union;
so it seems there might be an issues in tracking queries -> plan when the query
is broken up into multiple queries by Oak.
Looking at the Log entries in the tracer output, it shows the correct plan for
the query.
> Sling Log Tracer queries reports Plan that does not match Query statement
> -------------------------------------------------------------------------
>
> Key: SLING-6506
> URL: https://issues.apache.org/jira/browse/SLING-6506
> Project: Sling
> Issue Type: Bug
> Affects Versions: Log Tracer 0.0.2
> Reporter: David Gonzalez
> Attachments: tracer-error-output.txt, tracer-error-screencap.png
>
>
> The Queries data set from Sling Log Tracer (1.0.2) may report the wrong Query
> plan for the query.
> {noformat}
> "query": "//*[jcr:contains(.,
> '\"/content/dam/we-retail/en/people/mens/men_1.jpg\"')]",
> "plan": "[nt:unstructured] as [a] /*
> lucene:ntBaseLucene(/oak:index/ntBaseLucene)
> dam:resolvedPath:/content/dam/we-retail/en/people/mens/men_1.jpg where
> [a].[dam:resolvedPath] = '/content/dam/we-retail/en/people/mens/men_1.jpg' */"
> {noformat}
> Attached raw tracer output from Felix console.
> Explaining the query statement via Oak gives a different (and correct) plan.
> /cc [~chetanm]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
