hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13344) Add option to exclude Hadoop's SLF4J binding
Date Mon, 11 Jul 2016 16:52:11 GMT

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

Sean Busbey commented on HADOOP-13344:
--------------------------------------

yes, for client classpath we have been doing things wrong so far as SLF4J is concerned. (presuming
you think of the client classpath as being for using our code as a library to interact with
the cluster)

> Add option to exclude Hadoop's SLF4J binding
> --------------------------------------------
>
>                 Key: HADOOP-13344
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13344
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: bin, scripts
>    Affects Versions: 2.8.0, 2.7.2
>            Reporter: Thomas Poepping
>              Labels: patch
>         Attachments: HADOOP-13344.patch
>
>
> If another application that uses the Hadoop classpath brings in its own SLF4J binding
for logging, and that jar is not the exact same as the one brought in by Hadoop, then there
will be a conflict between logging jars between the two classpaths. This patch introduces
an optional setting to remove Hadoop's SLF4J binding from the classpath, to get rid of this
problem.
> This patch should be applied to 2.8.0, as bin/ and hadoop-config.sh structure has been
changed in 3.0.0.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message