[ 
https://issues.apache.org/jira/browse/IMPALA-9090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16962526#comment-16962526
 ] 

Xiaomeng Zhang commented on IMPALA-9090:
----------------------------------------

Hi [~tarmstrong], from query profile I can see table name after "SCAN HDFS"
{code:java}
00:SCAN HDFS [default.customers, RANDOM]
   HDFS partitions=1/1 files=1 size=15.44KB
   stored statistics:
     table: rows=0 size=15.44KB
     columns: all
   extrapolated-rows=disabled max-scan-range-rows=0
   mem-estimate=1.00MB mem-reservation=16.00KB thread-reservation=1
   tuple-ids=0 row-size=8B cardinality=0
   in pipelines: 00(GETNEXT)
{code}
Is there more info needed?

 

> Scan node in HDFS profile should include name of table being scanned
> --------------------------------------------------------------------
>
>                 Key: IMPALA-9090
>                 URL: https://issues.apache.org/jira/browse/IMPALA-9090
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend
>            Reporter: Tim Armstrong
>            Assignee: Xiaomeng Zhang
>            Priority: Critical
>
> The only way to figure out the table being scanned by a scan node in the 
> profile is to pull the string out of the explain plan or execsummary. This is 
> awkward, both for manual and automated analysis of the profiles. We should 
> include the table name as a string in the SCAN_NODE implementation.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to