[
https://issues.apache.org/jira/browse/TEZ-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14349650#comment-14349650
]
Jeff Zhang commented on TEZ-2162:
---------------------------------
Thanks for review [~bikassaha] [~hitesh] [~sseth] If you feel OK for the
following case, I will commit it. Paste it here again in case you miss it.
bq. But there's one exceptional case that if user specify OutputFormat through
conf, then even MROutput is on mapper side, user still need to use property
MRJobConfig.NEW_API_REDUCER_CONFIG rather than NEW_API_MAPPER_CONFIG. Or I
think we can take useNewAPI as true as any of NEW_API_MAPPER_CONFIG,
NEW_API_REDUCER_CONFIG is set true (patch didn't include this now)
> org.apache.hadoop.mapreduce.lib.output.SequenceFileOutputFormat is not
> recognized
> ---------------------------------------------------------------------------------
>
> Key: TEZ-2162
> URL: https://issues.apache.org/jira/browse/TEZ-2162
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.5.3
> Reporter: Oleg Zhurakousky
> Assignee: Jeff Zhang
> Priority: Critical
> Attachments: TEZ-2162-1.patch, TEZ-2162-2.patch
>
>
> {code}
> DataSinkDescriptor dataSink = MROutput.createConfigBuilder(dsConfig,
> outputFormatClass, outputPath).build();
> {code}
> if output format class is
> _org.apache.hadoop.mapreduce.lib.output.SequenceFileOutputFormat_ I end up
> with _TextOutputFormat_, however if it is
> _org.apache.hadoop.mapred.SequenceFileOutputFormat_, then all good.
> For now that can be a workaround to deal with SequenceFiles but I think that
> is the old API and it seems like Tez is having some issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
