[
https://issues.apache.org/jira/browse/HIVE-15531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15811016#comment-15811016
]
Prasanth Jayachandran commented on HIVE-15531:
----------------------------------------------
We used to have log4j-jcl bridge before when hive used both commons logging and
slf4j. We then moved hive completely use slf4j removing the log4j-jcl bridge as
it is no longer. This is the commit that moved to slf4j and remove log4j-jcl
bridge.
https://github.com/apache/hive/commit/a8ea6d82b0b6763f846848afeb5b338ab94e474a
Regarding the classpath ordering, we always force loading log4j2 jars first
before loading hadoop jars.
https://github.com/apache/hive/blob/master/bin/hive#L193
> Hive breaks Hadoop commons logging with log4j2
> ----------------------------------------------
>
> Key: HIVE-15531
> URL: https://issues.apache.org/jira/browse/HIVE-15531
> Project: Hive
> Issue Type: Bug
> Affects Versions: 2.1.0
> Reporter: Dhiraj Kumar
> Assignee: Dhiraj Kumar
> Priority: Minor
> Attachments: HIVE-15531.patch
>
>
> Hadoop (2.7), which is using Commons-logging is not compatible with log4j2
> without bridge.
> The bridge is missing in Hive.
> This leads to a problem whereby commons-logging initialises a log4j (1.2)
> version Logger, does not configure it properly since configuration for it is
> missing and sends logging output to stdout (the default).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
