You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Thomas Poepping (JIRA)" <ji...@apache.org> on 2016/09/14 17:30:20 UTC
[jira] [Updated] (HADOOP-13344) Add option to exclude Hadoop's
SLF4J binding
[ https://issues.apache.org/jira/browse/HADOOP-13344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Poepping updated HADOOP-13344:
-------------------------------------
Status: Patch Available (was: Open)
> 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.7.2, 2.8.0
> Reporter: Thomas Poepping
> Assignee: Thomas Poepping
> Labels: patch
> Attachments: HADOOP-13344.01.patch, 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