You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2015/12/02 10:31:11 UTC
[jira] [Assigned] (SPARK-12094) Better format for query plan tree
string
[ https://issues.apache.org/jira/browse/SPARK-12094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Apache Spark reassigned SPARK-12094:
------------------------------------
Assignee: Cheng Lian (was: Apache Spark)
> Better format for query plan tree string
> ----------------------------------------
>
> Key: SPARK-12094
> URL: https://issues.apache.org/jira/browse/SPARK-12094
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 1.7.0
> Reporter: Cheng Lian
> Assignee: Cheng Lian
> Priority: Minor
>
> When examine plans of complex queries with multiple joins, a pain point of mine is that, it's hard to immediately see the sibling node of a specific query plan node. For example:
> {noformat}
> TakeOrderedAndProject ...
> ConvertToSafe
> Project ...
> TungstenAggregate ...
> TungstenExchange ...
> TungstenAggregate ...
> Project ...
> BroadcastHashJoin ...
> Project ...
> BroadcastHashJoin ...
> Project ...
> BroadcastHashJoin ...
> Scan ...
> Filter ...
> Scan ...
> Scan ...
> Project ...
> Filter ...
> Scan ...
> {noformat}
> Would be better to have tree lines to indicate relationships between plan nodes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org