hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "zhuweimin (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-3227) Implement a binary input/output format for Streaming
Date Wed, 04 Mar 2009 02:20:56 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

zhuweimin updated HADOOP-3227:
------------------------------

    Attachment: hadoop-0.19.1-streaming.jar

> Implement a binary input/output format for Streaming
> ----------------------------------------------------
>
>                 Key: HADOOP-3227
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3227
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: contrib/streaming
>    Affects Versions: 0.19.1
>            Reporter: Arun C Murthy
>            Assignee: Arun C Murthy
>         Attachments: hadoop-0.19.1-streaming-20090303.diff, hadoop-0.19.1-streaming.jar
>
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message