sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abraham Elmahrek (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SQOOP-2350) Sqoop2: log4j properties file should be configurable
Date Wed, 06 May 2015 20:45:00 GMT
Abraham Elmahrek created SQOOP-2350:
---------------------------------------

             Summary: Sqoop2: log4j properties file should be configurable
                 Key: SQOOP-2350
                 URL: https://issues.apache.org/jira/browse/SQOOP-2350
             Project: Sqoop
          Issue Type: Bug
          Components: sqoop2-framework
    Affects Versions: 1.99.6
            Reporter: Abraham Elmahrek
             Fix For: 1.99.7


Currently, the MapReduce job that's kicked off will have the following configuration:
{code}
log4j.logger.org.apache.sqoop=INFO, A1

# A1 is set to be a ConsoleAppender.
log4j.appender.A1=org.apache.log4j.ConsoleAppender
log4j.appender.A1.Target   = System.err
log4j.appender.A1.layout=org.apache.log4j.PatternLayout
log4j.appender.A1.layout.ConversionPattern=%d{ISO8601} [%t] %-5p %c %x - %m%n
{code}

It's hard coded in the generated JAR file that we distribute. We should remove it from there
and make it configurable elsewhere.

Work around is to set {{mapreduce.job.log4j-properties-file}} in sqoop2 mapred-site.xml. See
MAPREDUCE-6052 for more info.



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

Mime
View raw message