You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Doug Cutting (JIRA)" <ji...@apache.org> on 2006/09/19 01:05:23 UTC

[jira] Resolved: (HADOOP-542) on-the-fly merge sort, HADOOP-540, reformat

     [ http://issues.apache.org/jira/browse/HADOOP-542?page=all ]

Doug Cutting resolved HADOOP-542.
---------------------------------

    Fix Version/s: 0.7.0
       Resolution: Fixed

I just committed this.  Thanks, Michel.

> on-the-fly merge sort, HADOOP-540, reformat
> -------------------------------------------
>
>                 Key: HADOOP-542
>                 URL: http://issues.apache.org/jira/browse/HADOOP-542
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: contrib/streaming
>         Environment: Tested on Linux and Windows
>            Reporter: Michel Tourn
>             Fix For: 0.7.0
>
>         Attachments: bigmux.patch2
>
>
> A large patch for streaming. Changes:
> Support for on-the-fly merge sort of multiple map input files.
> This supposes that the inputs are already sorted.
> Support for reducer-NONE side-effects to a single local output with DFS inputs.
> This can be used to do an on-the-fly merge-sort of remote sorted files.
> (Compare to DFSShell -getmerge which does *catenation* of remote sorted files)
> The single output can be a regular file, a named pipe or a socket.
> URI Syntax: -mapsideoutput [file:/C:/win|file:/unix/|socket://host:port]
> Add an optional JUnit test for on-the-fly merge-sort.
> It requires Unix tools. It also works with cygwin.
> If it has been more than 10 secs since last time we did this:
> call reporter.setStatus() when consuming a stderr line from the Application.
> Calling setStatus with reducer-NONE was already done as part of HADOOP-413.
> So overall this resolves HADOOP-540.
> Reformat streaming code to conform to Hadoop conventions 
>  (indent 2 spaces, opening bracket on same-line) 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira