hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dong Chen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-9120) Hive Query log does not work when hive.exec.parallel is true
Date Wed, 17 Dec 2014 08:08:13 GMT

     [ https://issues.apache.org/jira/browse/HIVE-9120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dong Chen updated HIVE-9120:
----------------------------
    Attachment: HIVE-9120.patch

My pleasure. Also thank [~chengxiang li] for finding this problem!
Patch attached. Changes are:
* Move OperationLog from hive-service to hive-exec, in order to avoid maven cyclic dependency
of these 2 module
* reset it in Driver and TaskRunner if parallel
* related changes caused by the movement


> 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
>         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
(v6.3.4#6332)

Mime
View raw message