Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <19781498.9261277197435356.JavaMail.jira@thor>
Date: Tue, 22 Jun 2010 05:03:55 -0400 (EDT)
From: "Ravi Gummadi (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Commented: (MAPREDUCE-1851) Document configuration
 parameters in streaming
In-Reply-To: <19160698.16701276144333988.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ravi Gummadi commented on MAPREDUCE-1851:
-----------------------------------------

The description of stream.joindelay.milli "Timeout in milliseconds for error thread and output thread to die" seems to be misleading if this is number of milli seconds for which the error thread and output thread are alive(time from start of thread to die). May be we should mention that this is the amount of time we wait for joining the error and output threads at the end of mapper/reducer ?

> Document configuration parameters in streaming
> ----------------------------------------------
>
>                 Key: MAPREDUCE-1851
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1851
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: contrib/streaming, documentation
>            Reporter: Amareshwari Sriramadasu
>            Assignee: Amareshwari Sriramadasu
>             Fix For: 0.22.0
>
>         Attachments: patch-1851-1.txt, patch-1851.txt
>
>
> There are several streaming options such as stream.map.output.field.separator, stream.num.map.output.key.fields, stream.map.input.field.separator,  stream.reduce.input.field.separator,  stream.map.input.ignoreKey, stream.non.zero.exit.is.failure etc which are spread everywhere. These should be documented at single place with description and default-value.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.