[
https://issues.apache.org/jira/browse/HIVE-14070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15344663#comment-15344663
]
Pengcheng Xiong commented on HIVE-14070:
----------------------------------------
[~ashutoshc] and [~sershe]. I also addressed some other problems which are
related with the "hive.tez.exec.print.summary=true". (1) original code L340 in
Driver.java, " PerfLogger perfLogger = SessionState.getPerfLogger();" this
should be reset otherwise the same PerfLogger will be reused across different
queries from the same session in CLI. (2) I removed "PerfLogger.TIME_TO_SUBMIT"
as it is never used. (3) I'm thinking about removing PerfLogger.DRIVER_RUN as
well. Right now it is used to denote the query start time. I would suggest use
the start time of PerfLogger.COMPILE instead.
> hive.tez.exec.print.summary=true returns wrong results on HS2
> -------------------------------------------------------------
>
> Key: HIVE-14070
> URL: https://issues.apache.org/jira/browse/HIVE-14070
> Project: Hive
> Issue Type: Sub-task
> Reporter: Pengcheng Xiong
> Assignee: Pengcheng Xiong
> Attachments: HIVE-14070.01.patch, HIVE-14070.02.patch
>
>
> On master, we have
> {code}
> Query Execution Summary
> ----------------------------------------------------------------------------------------------
> OPERATION DURATION
> ----------------------------------------------------------------------------------------------
> Compile Query -1466208820.74s
> Prepare Plan 0.00s
> Submit Plan 1466208825.50s
> Start DAG 0.26s
> Run DAG 4.39s
> ----------------------------------------------------------------------------------------------
> Task Execution Summary
> ----------------------------------------------------------------------------------------------
> VERTICES DURATION(ms) CPU_TIME(ms) GC_TIME(ms) INPUT_RECORDS
> OUTPUT_RECORDS
> ----------------------------------------------------------------------------------------------
> Map 1 1014.00 1,534 11 1,500
> 1
> Reducer 2 96.00 541 0 1
> 0
> ----------------------------------------------------------------------------------------------
> {code}
> sounds like a real issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
