You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/05/29 18:42:00 UTC
[jira] [Commented] (DRILL-6450) Visualized plans for profiles
querying JDBC sources is broken
[ https://issues.apache.org/jira/browse/DRILL-6450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16494039#comment-16494039 ]
ASF GitHub Bot commented on DRILL-6450:
---------------------------------------
kkhatua opened a new pull request #1295: DRILL-6450: Visualized plans for profiles querying JDBC sources is broken
URL: https://github.com/apache/drill/pull/1295
When viewing a profile for a query against a JDBC source, the visualized plan is not rendered. This is because the generated SQL pushed down to the JDBC source has a line break injected just before the FROM clause.
The workaround is to strip away any injected newlines ('\\n') at least for the SQL defined in the text plan, so that the backend Javascript can render it correctly.
In addition, any single line comments are also removed, but any block comments (i.e. /* .. */ ) are retained as they might carry hints.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
> Visualized plans for profiles querying JDBC sources is broken
> -------------------------------------------------------------
>
> Key: DRILL-6450
> URL: https://issues.apache.org/jira/browse/DRILL-6450
> Project: Apache Drill
> Issue Type: Bug
> Components: Query Planning & Optimization
> Affects Versions: 1.13.0
> Reporter: Kunal Khatua
> Assignee: Kunal Khatua
> Priority: Major
> Fix For: 1.14.0
>
>
> When viewing a profile for a query against a JDBC source, the visualized plan is not rendered. This is because the generated SQL pushed down to the JDBC source has a line break injected just before the {{FROM}} clause.
> The workaround is to strip away any injected newlines at least for the SQL defined in the text plan, so that the backend Javascript can render it correctly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)