You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Robert Metzger (JIRA)" <ji...@apache.org> on 2015/11/05 12:06:27 UTC

[jira] [Commented] (FLINK-2975) Exclude logging dependencies from shaded Hadoop jar.

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

Robert Metzger commented on FLINK-2975:
---------------------------------------

Thank you for opening the issue. I think we resolved this issue for Flink 0.10 here: FLINK-2703. As you can see from the pull request (https://github.com/apache/flink/pull/1194/files), we are excluding log4j from the shaded hadoop jar.

> Exclude logging dependencies from shaded Hadoop jar.
> ----------------------------------------------------
>
>                 Key: FLINK-2975
>                 URL: https://issues.apache.org/jira/browse/FLINK-2975
>             Project: Flink
>          Issue Type: Improvement
>          Components: Build System
>    Affects Versions: 0.9.1
>            Reporter: Jan Thomä
>
> The shaded hadoop jar has Log4j included. Therefore when you try to use flink with logback/slf4j logging you will get warnings like:
> ```
> log4j:WARN No appenders could be found for logger (kafka.consumer.SimpleConsumer).
> log4j:WARN Please initialize the log4j system properly.
> ```
> even when you have the appropriate slf4j bridges in the classpath. I'd suggest to exclude the Log4j dependency from the shaded Hadoop jar and then let the end user decide on wether he wants to add log4j or a slf4j bridge to the classpath.



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