Jason Lowe commented on HADOOP-15227:

Yeah, mapred-default and mapred-site aren't loaded until the JobConf class is 
loaded.  A common mistake for code is to create a plain Configuration early in 
{{main}} and try to lookup mapred properties (or even hdfs or yarn properties) 
expecting to get the default if they are not set by the user.  The easy fix is 
to create a JobConf instead of a Configuration if the code knows it wants to do 
mapred stuff.

> add mapreduce.outputcommitter.factory.scheme.s3a to core-default
> ----------------------------------------------------------------
>                 Key: HADOOP-15227
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15227
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 3.1.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Blocker
> Need to add this property to core-default.xml. It's documented as being 
> there, but it isn't.
> {code}
> <property>
>   <name>mapreduce.outputcommitter.factory.scheme.s3a</name>
>   <value>org.apache.hadoop.fs.s3a.commit.S3ACommitterFactory</value>
>   <description>
>     The committer factory to use when writing data to S3A filesystems.
>   </description>
> </property>
> {code}

This message was sent by Atlassian JIRA

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

Reply via email to