[ https://issues.apache.org/jira/browse/HADOOP-13344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371141#comment-15371141 ]
Allen Wittenauer commented on HADOOP-13344: ------------------------------------------- Reading http://www.slf4j.org/codes.html, I'm inclined to think we're doing this wrong in Hadoop. (Like that never happens...) Maybe we should pull the binding out, put it in a separate dir, then use a var to pull that dir in. I suspect that will break compatibility in 2.x though. (Although if hdfs-client can go in with it's insanity, this isn't much worse.) > 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-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org