[
https://issues.apache.org/jira/browse/HIVE-15531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15810881#comment-15810881
]
Dhiraj Kumar commented on HIVE-15531:
-------------------------------------
{quote} Does Hive logger still get log4j2, and Hadoop logger log4j? {quote}
It is possible if classpath is messed up. Will depend what extra library end
user has put in their classpath. That is exactly what happened in my case as
explained in earlier comment.
This patch makes sure that even if end users mess up their classpath (just from
log4j perspective), still logging will be setup properly and won't get into
log4j vs log4j2 issue.
I did not look it from the perspective of slf4j.
[~prasanth_j] can you have a look?
> 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)
