[
https://issues.apache.org/jira/browse/SPARK-23034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16321529#comment-16321529
]
Tejas Patil commented on SPARK-23034:
-------------------------------------
[~dongjoon] recommended that the scope of this JIRA could be extended to handle
scans which are going through codegen. As pointed out in the jira description,
for Spark native tables, the table scan node is abstracted out as a
`WholeStageCodegen` node in the DAG. I speculate there would be a class of
people who might say : A codegen node might be doing more things besides table
scan so it is not good to label it as `tablescan-tablename` unlike in case of
`HiveTableScan` where we know it doesn't do anything besides table scan.
We would like to get feedback from the community about this.
> Display tablename for `HiveTableScan` node in UI
> ------------------------------------------------
>
> Key: SPARK-23034
> URL: https://issues.apache.org/jira/browse/SPARK-23034
> Project: Spark
> Issue Type: Improvement
> Components: SQL, Web UI
> Affects Versions: 2.2.1
> Reporter: Tejas Patil
> Priority: Trivial
>
> For queries which scan multiple tables, it will be convenient if the DAG
> shown in Spark UI also showed which table is being scanned. This will make
> debugging easier. For this JIRA, I am scoping those for hive table scans
> only. For Spark native tables, the table scan node is abstracted out as a
> `WholeStageCodegen` node (which might be doing more things besides table
> scan).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
