[ https://issues.apache.org/jira/browse/HADOOP-12979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran updated HADOOP-12979: ------------------------------------ Description: Running some spark s3a tests trigger an NPE in Hadoop <=2/7l IOE in 2.8 saying {code} ${hadoop.tmp.dir}/s3a not configured. {code} That's correct: there is no configuration option on the conf called {code} ${hadoop.tmp.dir}/s3a {code} There may be one called {{hadoop.tmp.dir}}, however. Essentially s3a is sending the wrong config option down, if it can't find {{fs.s3a.buffer.dir}} was: Running some spark s3a tests trigger an NPE in Hadoop <=2/7l IOE in 2.8 saying "${hadoop.tmp.dir}/s3a not configured". That's correct: there is no configuration option on the conf called "${hadoop.tmp.dir}/s3a ". There may be one called {{hadoop.tmp.dir}}, however. Essentially s3a is sending the wrong config option down, if it can't find {{fs.s3a.buffer.dir}} > IOE in S3a: ${hadoop.tmp.dir}/s3a not configured > ------------------------------------------------- > > Key: HADOOP-12979 > URL: https://issues.apache.org/jira/browse/HADOOP-12979 > Project: Hadoop Common > Issue Type: Bug > Affects Versions: 2.8.0 > Reporter: Steve Loughran > > Running some spark s3a tests trigger an NPE in Hadoop <=2/7l IOE in 2.8 > saying > {code} > ${hadoop.tmp.dir}/s3a not configured. > {code} > That's correct: there is no configuration option on the conf called > {code} > ${hadoop.tmp.dir}/s3a > {code} > There may be one called {{hadoop.tmp.dir}}, however. > Essentially s3a is sending the wrong config option down, if it can't find > {{fs.s3a.buffer.dir}} -- This message was sent by Atlassian JIRA (v6.3.4#6332)