You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Zhihua Deng (Jira)" <ji...@apache.org> on 2022/01/16 13:54:00 UTC

[jira] [Commented] (HIVE-25850) hiveserver2 log can't access when "hive.session.id" has been set

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

Zhihua Deng commented on HIVE-25850:
------------------------------------

The logs is routed to another place where different from that the operation originally log to, same as https://issues.apache.org/jira/browse/HIVE-25158. In my opinion, we should not set the hive.session.id at runtime, it should be unique and seems unworthy to set it by hand.

> hiveserver2 log can't access when "hive.session.id" has been set
> ----------------------------------------------------------------
>
>                 Key: HIVE-25850
>                 URL: https://issues.apache.org/jira/browse/HIVE-25850
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>    Affects Versions: 3.1.2
>            Reporter: Jie Hu
>            Priority: Major
>
> Set "hive.session.id" when connect to hiveserver2 using beeline or jdbc, can't get log from console or "HiveStatement.getQueryLog()"



--
This message was sent by Atlassian Jira
(v8.20.1#820001)