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 22:54:05 UTC
[jira] [Resolved] (MAPREDUCE-393) Two small improvements to pipes
[ https://issues.apache.org/jira/browse/MAPREDUCE-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer resolved MAPREDUCE-393.
----------------------------------------
Resolution: Incomplete
Given that pipes was rewritten, I'm going to close this as stale.
> Two small improvements to pipes
> -------------------------------
>
> Key: MAPREDUCE-393
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-393
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Environment: n/a
> Reporter: Leon Mergen
> Assignee: Leon Mergen
> Attachments: nullpointer_fix.patch, pipes_interface.patch
>
>
> Working with the ..mapred.pipes class a bit today, I found one bug and one possible interface improvement:
> - Application.java in its constructor assumes that DistributedCache.getLocalCacheFiles () always returns non-zero, and returns an array with at least one element -- appropriate checks and exceptions should be thrown here.
> - Submitter.java provides a "submitJob ()" method, yet it acts like it's a runJob method (and also invokes mapred.JobClient.runClient ()) -- it should provide two interface methods, one runJob () and one submitJob (), who act just like the JobClient counterparts.
> Here is the small patch that implements both changes, based on the 0.17.1 release source -- just in case anyone cares for this minor improvement.
--
This message was sent by Atlassian JIRA
(v6.2#6252)