hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhiyuan Yang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13921) Remove Log4j classes from JobConf
Date Tue, 17 Oct 2017 05:37:00 GMT

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

Zhiyuan Yang commented on HADOOP-13921:

[~busbey] That helps to some extent, but I don't have confidence that people will always read
the doc. The best way to let people notice is to break their code as early as possible. Otherwise
rule without enforcement doesn't really make difference.

> Remove Log4j classes from JobConf
> ---------------------------------
>                 Key: HADOOP-13921
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13921
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: conf
>    Affects Versions: 3.0.0-alpha2
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Critical
>             Fix For: 3.0.0-alpha4
>         Attachments: HADOOP-13921.0.patch, HADOOP-13921.1.patch
> Replace the use of log4j classes from JobConf so that the dependency is not needed unless
folks are making use of our custom log4j appenders or loading a logging bridge to use that

This message was sent by Atlassian JIRA

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

View raw message