[
https://issues.apache.org/jira/browse/MAPREDUCE-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14042085#comment-14042085
]
Hadoop QA commented on MAPREDUCE-1362:
--------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12650130/MAPREDUCE-1362.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4681//console
This message is automatically generated.
> 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
> Affects Versions: trunk
> Reporter: Bassam Tabbara
> Fix For: trunk
>
> Attachments: MAPREDUCE-1362-trunk.patch, MAPREDUCE-1362.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.2#6252)
