hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13921) Remove Log4j classes from JobConf
Date Tue, 23 May 2017 16:18:04 GMT

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

Sean Busbey commented on HADOOP-13921:

bq. Is it basically that we're removing log4j from mapred client, so if users need log4j they'll
have to manually add it from now on?

It was a change in type. The patch as is doesn't alter where Log4j itself shows up as a dependency.
FWIW, the module this changes didn't list log4j as a dependency in the first place, it's relying
on it happening to get pulled in by maven from some other dependency.

> 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
>         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