[
https://issues.apache.org/jira/browse/AMBARI-8265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14205694#comment-14205694
]
Hudson commented on AMBARI-8265:
--------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit-docker #194 (See
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/194/])
AMBARI-8265. Ambari hive-log4j.properties should output the thread id
(alejandro) (afernandez:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=31e118f96f08f6889ec7f8cce1e8cda558d26363)
*
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HIVE/configuration/hive-log4j.xml
> Ambari hive-log4j.properties should output the thread id
> --------------------------------------------------------
>
> Key: AMBARI-8265
> URL: https://issues.apache.org/jira/browse/AMBARI-8265
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 1.7.0
> Reporter: Alejandro Fernandez
> Assignee: Alejandro Fernandez
> Priority: Critical
> Fix For: 1.7.0
>
> Attachments: AMBARI-8265.patch
>
>
> In HIVE-6876
> (https://github.com/hortonworks/hive/blob/champlain/common/src/main/resources/hive-log4j.properties),
> we added better logging to log thread-ids. Without this, any sort of
> debugging which involves tracking the flow of a query through server threads,
> becomes very difficult. For some reason, I don't see the thread id logging
> pattern ([%t]) in the hive-log4j.properties that gets put into the conf
> directory.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
