hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dhiraj Kumar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-15531) Hive breaks Hadoop commons logging with log4j2
Date Mon, 09 Jan 2017 11:50:58 GMT

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

Dhiraj Kumar commented on HIVE-15531:
-------------------------------------

If commons-logging is not used by hive then log4j-jcl is not required. But if commons-logging
is being used by Hadoop, a bridge will be required. By default log4j-1.2-api acts as bridge
for hadoop logging which had been added in the commit 

https://github.com/apache/hive/commit/c93d6c77e31e2eb9b40f5167ab3491d44eae351a

Also agree that with classpath properly ordered, this issue will not surface at all. 

I would have liked it with log4j-jcl, removing classpath ordering dependency as well as user
lib into classpath (coming higher than hive log4j's lib)

I will leave it to you and will close the discussion here. 





> 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)

Mime
View raw message