Using the default constructor here means the TaskID will default to 0 I think.
I believe it is the case that temporary files can end up in
`${mapreduce.output.fileoutputformat.outputdir}/_temporary/_${taskid}` and
without a real `TaskID` is it possible there can be a file naming collision
here?
See
http://hadoop.apache.org/docs/r2.7.0/hadoop-mapreduce-client/hadoop-mapreduce-client-core/MapReduceTutorial.html#Task_Side-Effect_Files
[ Full content available at: https://github.com/apache/beam/pull/6306 ]
This message was relayed via gitbox.apache.org for [email protected]
