Max Thompson created SPARK-30367:
------------------------------------
Summary: 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.0.0
Reporter: Max Thompson
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:
!SKF6TLGsAAAAASUVORK5CYII=!
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:
!E0KYCAIKYAALQQMQUAoIWIKQAALURMAQBoIWIKAEALEVMAAFqImAIA0ELEFACAFiKmAAC0EDEFAKCFiCkAAC1ETAEAaCFiCgBACxFTAABa6H8BsISskzFa3iEAAAAASUVORK5CYII=!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
