[
https://issues.apache.org/jira/browse/HIVE-15631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823090#comment-15823090
]
ASF GitHub Bot commented on HIVE-15631:
---------------------------------------
GitHub user Tartarus0zm opened a pull request:
https://github.com/apache/hive/pull/132
#HIVE-15631
if set hive.log.reload.variable.enable is true, and use hive.session.id in
hive-log4j2.properties ,
then will print hive.session.id on logs
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Tartarus0zm/hive reload_log4j_variable
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/hive/pull/132.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #132
----
commit 5cb250b803ce36ee02b0d6c637edfe4b0a9376f3
Author: Tartarus <zhangm...@jd.com>
Date: 2017-01-15T09:54:08Z
#HIVE-15631
if set hive.log.reload.variable.enable is true, and use hive.session.id in
hive-log4j2.properties ,
then will print hive.session.id on logs
----
> Optimize for hive client logs , you can filter the log for each session
> itself.
> -------------------------------------------------------------------------------
>
> Key: HIVE-15631
> URL: https://issues.apache.org/jira/browse/HIVE-15631
> Project: Hive
> Issue Type: Improvement
> Components: CLI, Clients, Hive
> Reporter: tartarus
> Assignee: tartarus
> Attachments: HIVE_15631.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> We have several hadoop cluster, about 15 thousand nodes. Every day we use
> hive to submit above 100 thousand jobs.
> So we have a large file of hive logs on every client host every day, but i
> don not know the logs of my session submitted was which line.
> So i hope to print the hive.session.id on every line of logs, and then i
> could use grep to find the logs of my session submitted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
