[
https://issues.apache.org/jira/browse/HIVE-9496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14304179#comment-14304179
]
Thejas M Nair commented on HIVE-9496:
-------------------------------------
hive-jdbc-standalone jar should not be including an slf4j binding. This jar is
meant to be used by an external application, and that application should have
control over what logging framework is used (including alternatives to log4j).
I think we need to remove slf4j binding from this jar.
Regarding, the move to extlib, we can consider that if we have very strong
reasons to do so. Moving the dir would mean that client applications might
break on upgrade, since their classpaths would point to the jar in lib dir.
> Slf4j warning in hive command
> -----------------------------
>
> Key: HIVE-9496
> URL: https://issues.apache.org/jira/browse/HIVE-9496
> Project: Hive
> Issue Type: Bug
> Components: CLI
> Affects Versions: 0.14.0
> Environment: HDP 2.2.0 on CentOS.
> With Horton Sand Box and my own cluster.
> Reporter: Philippe Kernevez
> Assignee: Alexander Pivovarov
> Priority: Minor
> Attachments: HIVE-9496.1.patch
>
>
> Each time 'hive' command is ran, we have an Sl4J warning about multiple jars
> containing SL4J classes.
> This bug is similar to Hive-6162, but doesn't seems to be solved.
> Logging initialized using configuration in
> file:/etc/hive/conf/hive-log4j.properties
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/usr/hdp/2.2.0.0-1084/hadoop/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/usr/hdp/2.2.0.0-1084/hive/lib/hive-jdbc-0.14.0.2.2.0.0-1084-standalone.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.slf4j.impl.Log4jLoggerFactory]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
