[ https://issues.apache.org/jira/browse/MAPREDUCE-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran resolved MAPREDUCE-6961. --------------------------------------- Resolution: Duplicate Fix Version/s: 3.1.0 This went in with HADOOP-13786 > Pull up FileOutputCommitter.getOutputPath to PathOutputCommitter > ---------------------------------------------------------------- > > Key: MAPREDUCE-6961 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6961 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: mrv2 > Affects Versions: 3.0.0-beta1 > Reporter: Steve Loughran > Assignee: Steve Loughran > Priority: Minor > Fix For: 3.1.0 > > > SPARK-21549 has shown that downstream code is relying on the internal > property > if we pulled {{FileOutputCommitter.getOutputPath}} to the > {{PathOutputCommitter}} of MAPREDUCE-6956, then there'd be a public/stable > way to get this. Admittedly, it does imply that the committer will always > have *some* output path, but FileOutputFormat depends on that anyway. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: mapreduce-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-dev-h...@hadoop.apache.org