[
https://issues.apache.org/jira/browse/TEZ-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14347359#comment-14347359
]
Hitesh Shah commented on TEZ-2162:
----------------------------------
A test for this is needed. For the case of a map-only MR job, does this work?
i.e. should use new api check be based on whether it is a mapper/reducer? In
any case, relying on one of the two is probably not useful for Pig/Hive which
dont use MR processors. Is there a way to explicitly configure which api via
the config builder?
> 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
>
>
> {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)
