hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-1362) Pipes should be ported to the new mapreduce API
Date Fri, 08 May 2015 23:49:01 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535933#comment-14535933

Allen Wittenauer commented on MAPREDUCE-1362:

I ran a local test-patch.sh which reports the build fails with this patch in place.  We'll
wait for the official one, but I expect this patch needs some work for modern trunk.

> Pipes should be ported to the new mapreduce API
> -----------------------------------------------
>                 Key: MAPREDUCE-1362
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1362
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: pipes
>            Reporter: Bassam Tabbara
>              Labels: BB2015-05-TBR
>         Attachments: MAPREDUCE-1362-trunk.patch, MAPREDUCE-1362.patch, MAPREDUCE-1362.patch
> Pipes is still currently using the old mapred API. This prevents us from using pipes
with HBase's TableInputFormat, HRegionPartitioner, etc. 
> Here is a rough proposal for how to accomplish this:
> * Add a new package org.apache.hadoop.mapreduce.pipes that uses the new mapred API.
> * the new pipes package will run side by side with the old one. old one should get deprecated
at some point.
> * the wire protocol used between PipesMapper and PipesReducer and C++ programs must not
> * bin/hadoop should support both pipes (old api) and pipes2 (new api)
> Does this sound reasonable?

This message was sent by Atlassian JIRA

View raw message