[
https://issues.apache.org/jira/browse/HIVE-11488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15033421#comment-15033421
]
Lefty Leverenz commented on HIVE-11488:
---------------------------------------
Doc note: [~aihuaxu] documented this in the HiveServer2 Clients wikidoc so I'm
removing the TODOC2.0 label.
* [HiveServer2 Clients -- HiveServer2 Logging |
https://cwiki.apache.org/confluence/display/Hive/HiveServer2+Clients#HiveServer2Clients-HiveServer2Logging]
> Add sessionId and queryId info to HS2 log
> -----------------------------------------
>
> Key: HIVE-11488
> URL: https://issues.apache.org/jira/browse/HIVE-11488
> Project: Hive
> Issue Type: New Feature
> Components: Logging
> Affects Versions: 2.0.0
> Reporter: Aihua Xu
> Assignee: Aihua Xu
> Fix For: 2.0.0
>
> Attachments: HIVE-11488.2.patch, HIVE-11488.3.patch, HIVE-11488.patch
>
>
> Session is critical for a multi-user system like Hive. Currently Hive doesn't
> log seessionId to the log file, which sometimes make debugging and analysis
> difficult when multiple activities are going on at the same time and the log
> from different sessions are mixed together.
> Currently, Hive already has the sessionId saved in SessionState and also
> there is another sessionId in SessionHandle (Seems not used and I'm still
> looking to understand it). Generally we should have one sessionId from the
> beginning in the client side and server side. Seems we have some work on that
> side first.
> The sessionId then can be added to log4j supported mapped diagnostic context
> (MDC) and can be configured to output to log file through the log4j property.
> MDC is per thread, so we need to add sessionId to the HS2 main thread and
> then it will be inherited by the child threads.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
