[ https://issues.apache.org/jira/browse/IMPALA-9090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16962545#comment-16962545 ]
Tim Armstrong commented on IMPALA-9090: --------------------------------------- [~Xiaomeng Zhang] that's in the embedded explain plan, we want it in the actual scan node in the profile, like this bit: {noformat} HDFS_SCAN_NODE (id=2):(Total: 1s194ms, non-child: 1s194ms, % non-child: 100.00%) - BytesRead: 0 - MaterializeTupleTime(*): 0.000ns - NumScannerThreadMemUnavailable: 0 (0) - NumScannerThreadReservationsDenied: 0 (0) - NumScannerThreadsStarted: 0 (0) - PeakMemoryUsage: 0 - RowBatchBytesEnqueued: 0 - RowBatchQueueGetWaitTime: 0.000ns - RowBatchQueuePeakMemoryUsage: 0 - RowBatchQueuePutWaitTime: 0.000ns - RowBatchesEnqueued: 0 (0) - RowsRead: 0 (0) - RowsReturned: 0 (0) - RowsReturnedRate: 0 - ScannerThreadWorklessLoops: 0 (0) - ScannerThreadsInvoluntaryContextSwitches: 0 (0) - ScannerThreadsTotalWallClockTime: 0.000ns - ScannerThreadsSysTime: 0.000ns - ScannerThreadsUserTime: 0.000ns - ScannerThreadsVoluntaryContextSwitches: 0 (0) - TotalReadThroughput: 0.00 /sec {noformat} > 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: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org