You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/05/06 20:44:04 UTC
[jira] [Commented] (SLING-6506) Sling Log Tracer queries reports
Plan that does not match Query statement
[ https://issues.apache.org/jira/browse/SLING-6506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999577#comment-15999577 ]
ASF GitHub Bot commented on SLING-6506:
---------------------------------------
GitHub user davidjgonzalez opened a pull request:
https://github.com/apache/sling/pull/223
SLING-6506 - Tracer - Fixed query/plan correlation when union'd queri…
…es are followed by 1+ queries
Resolves: https://issues.apache.org/jira/browse/SLING-6506
Example output post patch (addressing erring use-case in SLING-6505 ticket)
![image](https://cloud.githubusercontent.com/assets/1451868/25775762/d4c1ee26-327a-11e7-8115-89a9dcadcc79.png)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/davidjgonzalez/sling SLING-6506
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/sling/pull/223.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #223
----
commit db873792e2e7c050b9e5160745fe2bfe8a3d098f
Author: david g <da...@gmail.com>
Date: 2017-05-06T20:38:20Z
SLING-6506 - Tracer - Fixed query/plan correlation when union'd queries are followed by 1+ queries
----
> 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
> Assignee: Chetan Mehrotra
> Fix For: Log Tracer 1.0.2
>
> 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)