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 "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/18 07:11:06 UTC
[jira] [Resolved] (MAPREDUCE-606) Implement a binary input/output
format for Streaming
[ https://issues.apache.org/jira/browse/MAPREDUCE-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer resolved MAPREDUCE-606.
----------------------------------------
Resolution: Fixed
I'm closing this as fixed. The streaming input/output system has been enhanced since this jira was filed.
> Implement a binary input/output format for Streaming
> ----------------------------------------------------
>
> Key: MAPREDUCE-606
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-606
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: contrib/streaming
> Reporter: Arun C Murthy
> Attachments: hadoop-3227.patch
>
>
> Lots of streaming applications process textual data with 1 record per line and fields separated by a delimiter. It turns out that there is no point in using any of Hadoop's input/output formats since the streaming script/binary itself will parse the input and break into records and fields. In such cases we should provide users with a binary input/output format which just sends 64k (or so) blocks of data directly from HDFS to the streaming application.
> I did something very similar for Pig-Streaming (PIG-94 - BinaryStorage) which resulted in 300%+ speedup for scanning (identity mapper & map-only jobs) data... the parsing done by input/output formats in these cases were pure-overhead.
--
This message was sent by Atlassian JIRA
(v6.2#6252)