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 2015/05/09 01:13:01 UTC

[jira] [Commented] (MAPREDUCE-1362) Pipes should be ported to the new mapreduce API

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

Allen Wittenauer commented on MAPREDUCE-1362:
---------------------------------------------

Kicked off a fresh Jenkins run.  Not sure why there isn't one.

> 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 change.
> * bin/hadoop should support both pipes (old api) and pipes2 (new api)
> Does this sound reasonable?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)