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

xialu commented on HIVE-9120:
-----------------------------

when hive's code update to branch 3.0, log4j1 update to log4j2, class Driver 
removed OperationLog. beeline query progress information can not retrieve too.

> Hive Query log does not work when hive.exec.parallel is true
> ------------------------------------------------------------
>
>                 Key: HIVE-9120
>                 URL: https://issues.apache.org/jira/browse/HIVE-9120
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2, Logging
>            Reporter: Dong Chen
>            Assignee: Dong Chen
>            Priority: Major
>             Fix For: 1.1.0
>
>         Attachments: HIVE-9120.patch
>
>
> When hive.exec.parallel is true, the query log is not saved and Beeline can 
> not retrieve it.
> When parallel, Driver.launchTask() may run the task in a new thread if other 
> conditions are also on. TaskRunner.start() is invoked instead of 
> TaskRunner.runSequential(). This cause the threadlocal variable OperationLog 
> to be null and query logs are not logged.
> The OperationLog object should be set in the new thread in this case.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to