Todd Lipcon created HIVE-21688:
----------------------------------
Summary: SLF4J binding warning message printed when invoking
beeline
Key: HIVE-21688
URL: https://issues.apache.org/jira/browse/HIVE-21688
Project: Hive
Issue Type: Bug
Affects Versions: 4.0.0
Reporter: Todd Lipcon
When I run beeline (or any other hive tool), it outputs the following:
{code}
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/data/1/todd/impala/toolchain/cdp_components-1056671/apache-hive-3.1.0.6.0.99.0-147-bin/lib/log4j-slf4j-impl-2.10.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/data/1/todd/impala/toolchain/cdp_components-1056671/hadoop-3.1.1.6.0.99.0-147/share/hadoop/common/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]
{code}
It seems that Hive moved to log4j2 in HIVE-11304 and started bundling the
log4j2 slf4j binding in HIVE-13015. Hadoop is still on log4j 1, so the SLF4J
bindings are conflicting and producing these errors on stderr. This may confuse
users, and makes it hard to understand which log4j properties files are getting
used.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
