[ https://issues.apache.org/jira/browse/SPARK-12094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15035539#comment-15035539 ]
Apache Spark commented on SPARK-12094: -------------------------------------- User 'liancheng' has created a pull request for this issue: https://github.com/apache/spark/pull/10099 > 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-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org