You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2018/03/22 03:20:00 UTC
[jira] [Updated] (MAPREDUCE-6961) Pull up
FileOutputCommitter.getOutputPath to PathOutputCommitter
[ https://issues.apache.org/jira/browse/MAPREDUCE-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kumar Vavilapalli updated MAPREDUCE-6961:
-----------------------------------------------
Fix Version/s: (was: 3.1.0)
Removing 3.1.0 fix-version from all JIRAs which are Invalid / Won't Fix / Duplicate / Cannot Reproduce.
> 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
>
> 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-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org