[
https://issues.apache.org/jira/browse/HIVE-18472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16334998#comment-16334998
]
Vihang Karajgaonkar commented on HIVE-18472:
--------------------------------------------
Lets update the comment to make it clear that we are excluding Hive's log4j
jars from the CLASSPATH before executing hadoop and hbase commands from the
script. Hadoop and hbase use their log4j bindings and we add the Hive's log4j
binding in the end. This gets rid of the annoying log4j warning before starting
beeline. Thanks [~janulatha] for fixing this.
+1
> Beeline gives log4j warnings
> ----------------------------
>
> Key: HIVE-18472
> URL: https://issues.apache.org/jira/browse/HIVE-18472
> Project: Hive
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Janaki Lahorani
> Assignee: Janaki Lahorani
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: HIVE-18472.1.patch
>
>
> Starting Beeline gives the following warnings multiple times:
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/opt/cloudera/parcels/CDH-6.x-1.cdh6.x.p0.215261/jars/log4j-slf4j-impl-2.8.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/opt/cloudera/parcels/CDH-6.x-1.cdh6.x.p0.215261/jars/slf4j-log4j12-1.7.5.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]
> ERROR StatusLogger No log4j2 configuration file found. Using default
> configuration: logging only errors to the console. Set system property
> 'org.apache.logging.log4j.simplelog.StatusLogger.level' to TRACE to show
> Log4j2 internal initialization logging.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
