[jira] [Commented] (OAK-8245) Add column for explained "statement" to "explain" Query result, next to 'plan' column.
[ https://issues.apache.org/jira/browse/OAK-8245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16929170#comment-16929170 ] Thomas Mueller commented on OAK-8245: - svn.apache.org/r1866903 (trunk) > Add column for explained "statement" to "explain" Query result, next to > 'plan' column. > -- > > Key: OAK-8245 > URL: https://issues.apache.org/jira/browse/OAK-8245 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: query >Affects Versions: 1.12.0, 1.8.12, 1.10.2 >Reporter: Mark Adamcin >Assignee: Thomas Mueller >Priority: Minor > > The "explain" behavior of the core Query is very useful for helping to debug > JCR query execution planning. For xpath queries, the resulting "plan" column > refers to the result of running XPathToSQL2Converter to produce a JCR-SQL2 > statement for execution. This SQL2 statement should be exposed through the > same API as the "plan", by way of an additional column named "statement" in > the single result row. > At this time, this underlying SQL2 statement is inaccessible to users of the > JCR Query interface, which can only provide the original XPath statement. > To access the converted SQL2 statement, a class targeting the JCR API must > implement a regular expression match against a log stream retrieved via slf4j > MDC. > This facility is not very portable, and an effective pattern on one version > of Oak may not be effective on a different version of Oak, for any number of > reasons. > Also, the XPathToSQL2Converter package is not exported in an OSGi > environment, so client code cannot use that API to reconstruct the SQL2 > statement in parallel. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (OAK-8245) Add column for explained "statement" to "explain" Query result, next to 'plan' column.
[ https://issues.apache.org/jira/browse/OAK-8245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16820576#comment-16820576 ] Mark Adamcin commented on OAK-8245: --- Thanks, [~tmueller]. I appreciate it. > Add column for explained "statement" to "explain" Query result, next to > 'plan' column. > -- > > Key: OAK-8245 > URL: https://issues.apache.org/jira/browse/OAK-8245 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: query >Affects Versions: 1.12.0, 1.8.12, 1.10.2 >Reporter: Mark Adamcin >Assignee: Thomas Mueller >Priority: Minor > > The "explain" behavior of the core Query is very useful for helping to debug > JCR query execution planning. For xpath queries, the resulting "plan" column > refers to the result of running XPathToSQL2Converter to produce a JCR-SQL2 > statement for execution. This SQL2 statement should be exposed through the > same API as the "plan", by way of an additional column named "statement" in > the single result row. > At this time, this underlying SQL2 statement is inaccessible to users of the > JCR Query interface, which can only provide the original XPath statement. > To access the converted SQL2 statement, a class targeting the JCR API must > implement a regular expression match against a log stream retrieved via slf4j > MDC. > This facility is not very portable, and an effective pattern on one version > of Oak may not be effective on a different version of Oak, for any number of > reasons. > Also, the XPathToSQL2Converter package is not exported in an OSGi > environment, so client code cannot use that API to reconstruct the SQL2 > statement in parallel. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-8245) Add column for explained "statement" to "explain" Query result, next to 'plan' column.
[ https://issues.apache.org/jira/browse/OAK-8245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16819768#comment-16819768 ] Thomas Mueller commented on OAK-8245: - Thanks [~madamcin]! I agree it is useful to add the SQL-2 statement, specially to understand "union" conversions and so on. I will try to merge the patch; this may take a few days. > Add column for explained "statement" to "explain" Query result, next to > 'plan' column. > -- > > Key: OAK-8245 > URL: https://issues.apache.org/jira/browse/OAK-8245 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: query >Affects Versions: 1.12.0, 1.8.12, 1.10.2 >Reporter: Mark Adamcin >Assignee: Thomas Mueller >Priority: Minor > > The "explain" behavior of the core Query is very useful for helping to debug > JCR query execution planning. For xpath queries, the resulting "plan" column > refers to the result of running XPathToSQL2Converter to produce a JCR-SQL2 > statement for execution. This SQL2 statement should be exposed through the > same API as the "plan", by way of an additional column named "statement" in > the single result row. > At this time, this underlying SQL2 statement is inaccessible to users of the > JCR Query interface, which can only provide the original XPath statement. > To access the converted SQL2 statement, a class targeting the JCR API must > implement a regular expression match against a log stream retrieved via slf4j > MDC. > This facility is not very portable, and an effective pattern on one version > of Oak may not be effective on a different version of Oak, for any number of > reasons. > Also, the XPathToSQL2Converter package is not exported in an OSGi > environment, so client code cannot use that API to reconstruct the SQL2 > statement in parallel. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-8245) Add column for explained "statement" to "explain" Query result, next to 'plan' column.
[ https://issues.apache.org/jira/browse/OAK-8245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16819723#comment-16819723 ] Vikas Saurabh commented on OAK-8245: [~tmueller], maybe you? > Add column for explained "statement" to "explain" Query result, next to > 'plan' column. > -- > > Key: OAK-8245 > URL: https://issues.apache.org/jira/browse/OAK-8245 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: query >Affects Versions: 1.12.0, 1.8.12, 1.10.2 >Reporter: Mark Adamcin >Priority: Minor > > The "explain" behavior of the core Query is very useful for helping to debug > JCR query execution planning. For xpath queries, the resulting "plan" column > refers to the result of running XPathToSQL2Converter to produce a JCR-SQL2 > statement for execution. This SQL2 statement should be exposed through the > same API as the "plan", by way of an additional column named "statement" in > the single result row. > At this time, this underlying SQL2 statement is inaccessible to users of the > JCR Query interface, which can only provide the original XPath statement. > To access the converted SQL2 statement, a class targeting the JCR API must > implement a regular expression match against a log stream retrieved via slf4j > MDC. > This facility is not very portable, and an effective pattern on one version > of Oak may not be effective on a different version of Oak, for any number of > reasons. > Also, the XPathToSQL2Converter package is not exported in an OSGi > environment, so client code cannot use that API to reconstruct the SQL2 > statement in parallel. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-8245) Add column for explained "statement" to "explain" Query result, next to 'plan' column.
[ https://issues.apache.org/jira/browse/OAK-8245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16819457#comment-16819457 ] Mark Adamcin commented on OAK-8245: --- [~catholicon] would you be willing to review this? > Add column for explained "statement" to "explain" Query result, next to > 'plan' column. > -- > > Key: OAK-8245 > URL: https://issues.apache.org/jira/browse/OAK-8245 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: query >Affects Versions: 1.12.0, 1.8.12, 1.10.2 >Reporter: Mark Adamcin >Priority: Minor > > The "explain" behavior of the core Query is very useful for helping to debug > JCR query execution planning. For xpath queries, the resulting "plan" column > refers to the result of running XPathToSQL2Converter to produce a JCR-SQL2 > statement for execution. This SQL2 statement should be exposed through the > same API as the "plan", by way of an additional column named "statement" in > the single result row. > At this time, this underlying SQL2 statement is inaccessible to users of the > JCR Query interface, which can only provide the original XPath statement. > To access the converted SQL2 statement, a class targeting the JCR API must > implement a regular expression match against a log stream retrieved via slf4j > MDC. > This facility is not very portable, and an effective pattern on one version > of Oak may not be effective on a different version of Oak, for any number of > reasons. > Also, the XPathToSQL2Converter package is not exported in an OSGi > environment, so client code cannot use that API to reconstruct the SQL2 > statement in parallel. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
