You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Dongjoon Hyun (Jira)" <ji...@apache.org> on 2020/03/16 22:51:08 UTC
[jira] [Updated] (SPARK-30367) De-duplicate InMemoryTableScan
cached plans in SQL UI
[ https://issues.apache.org/jira/browse/SPARK-30367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dongjoon Hyun updated SPARK-30367:
----------------------------------
Affects Version/s: (was: 3.0.0)
3.1.0
> De-duplicate InMemoryTableScan cached plans in SQL UI
> -----------------------------------------------------
>
> Key: SPARK-30367
> URL: https://issues.apache.org/jira/browse/SPARK-30367
> Project: Spark
> Issue Type: Improvement
> Components: SQL, Web UI
> Affects Versions: 3.1.0
> Reporter: Max Thompson
> Priority: Minor
> Attachments: deduplicated-imr.png, duplicated-imr.png
>
>
> This is a follow-up JIRA for: https://issues.apache.org/jira/browse/SPARK-29431
> Currently with the change introduced by the JIRA this follows up on, duplicate subtrees of the query plan can be shown if multiple InMemoryTableScans read from the same persisted data:
> !duplicated-imr.png!
> To prevent confusion, we should add an "InMemoryRelation" node that represents the persisted data being read from, and use it to de-duplicate shared plans like so:
> !deduplicated-imr.png!
--
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