[
https://issues.apache.org/jira/browse/HADOOP-13344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15365228#comment-15365228
]
Thomas Poepping commented on HADOOP-13344:
------------------------------------------
That was my mistake, I didn't mean to include 2.7.2 as a target version, only
2.8.0.
I found while writing this that we could use 'jar tf ${jarname}', but that was
always much slower than grepping the jarfile directly.
As far as documentation, I don't have any plans. I assume that any
documentation that already exists regarding hadoop-config.sh should have this
feature documented. As far as client applications have documentation, I don't
see any good way to do it. We can't very well change the documentation of each
application depending on Hadoop. It could also be added to a hadoop-config help
method, if one exists. I'll look into it.
First and foremost though -- I'll be targeting trunk. The reason I targeted
this directly is because the structure of the hadoop-config file is very
different in trunk.
> 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: [email protected]
For additional commands, e-mail: [email protected]
