You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (Jira)" <ji...@apache.org> on 2021/09/23 06:57:00 UTC
[jira] [Resolved] (SPARK-36795) Explain Formatted has Duplicated
Node IDs with InMemoryRelation Present
[ https://issues.apache.org/jira/browse/SPARK-36795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyukjin Kwon resolved SPARK-36795.
----------------------------------
Fix Version/s: 3.2.1
Resolution: Fixed
Fixed in https://github.com/apache/spark/pull/34036
> Explain Formatted has Duplicated Node IDs with InMemoryRelation Present
> -----------------------------------------------------------------------
>
> Key: SPARK-36795
> URL: https://issues.apache.org/jira/browse/SPARK-36795
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 3.1.2
> Reporter: Michael Chen
> Priority: Major
> Fix For: 3.2.1
>
>
> When a query contains an InMemoryRelation, the output of Explain Formatted will contain duplicate node IDs.
> {code:java}
> == Physical Plan ==
> AdaptiveSparkPlan (14)
> +- == Final Plan ==
> * BroadcastHashJoin Inner BuildLeft (9)
> :- BroadcastQueryStage (5)
> : +- BroadcastExchange (4)
> : +- * Filter (3)
> : +- * ColumnarToRow (2)
> : +- InMemoryTableScan (1)
> : +- InMemoryRelation (2)
> : +- * ColumnarToRow (4)
> : +- Scan parquet default.t1 (3)
> +- * Filter (8)
> +- * ColumnarToRow (7)
> +- Scan parquet default.t2 (6)
> +- == Initial Plan ==
> BroadcastHashJoin Inner BuildLeft (13)
> :- BroadcastExchange (11)
> : +- Filter (10)
> : +- InMemoryTableScan (1)
> : +- InMemoryRelation (2)
> : +- * ColumnarToRow (4)
> : +- Scan parquet default.t1 (3)
> +- Filter (12)
> +- Scan parquet default.t2 (6)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org