Max Thompson created SPARK-30369:
------------------------------------
Summary: Prune uncomputed children of InMemoryRelation
Key: SPARK-30369
URL: https://issues.apache.org/jira/browse/SPARK-30369
Project: Spark
Issue Type: Improvement
Components: SQL, Web UI
Affects Versions: 3.0.0
Reporter: Max Thompson
This is a follow-up JIRA for: [De-duplicate InMemoryTableScan cached plans in
SQL UI JIRA URL]
Currently with the changes introduced by the JIRAs this follows up on, if a
query persists data that is later read by another query, the uncomputed subtree
of the plan for the persisted data will be shown:
!bLgZ04NuAvvtXpD8SABA
xBkAgChDnAEAiDLEGQCAKEOcAQCIMsQZAIAoQ5wBAIgyxBkAgChDnAEAiDLEGQCAKEOcAQCIMsQZAIAoQ5wBAIgyxBkAgChDnAEAiDLEGQCAKEOcAQCIMv8P7NCckWtEmyMAAAAASUVORK5CYII=!
To avoid showing uncomputed subtrees in the query plan (which may become
appreciably large in a situation such as if multiple iterative queries are run
that each use persisted data from the last query), the uncomputed subtrees
could be removed before rendering the query plan:
!dGo9o
CEEIYSEIIIcQcDCQhhBBiBgaSEEIIMQMDSQghhJiBgSSEEELMwEASQgghZmAgCSGEEDMwkIQQQogZGEhCCCHEDAwkIYQQYgYGkhBCCDEDA0kIIYSYgYEkhBBCzMBAEkIIIWZgIAkhhBAzMJCEEEKIGRhIQgghxAwMJCGEEGIGBpIQQggxAwNJCCGEmIGBJIQQQszAQBJCCCFm
P8Bum1cUi kSH0AAAAASUVORK5CYII=!
A configuration property should be added that enables this feature when set to
true. If a user wants to see the uncomputed subtrees, they can simply disable
the configuration property.
--
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
