Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <20811297.1170950167232.JavaMail.jira@brutus>
Date: Thu, 8 Feb 2007 07:56:07 -0800 (PST)
From: "Arun C Murthy (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Updated: (HADOOP-977) The output from the user's task should
 be tagged and sent to the resepective console streams.
In-Reply-To: <16739725.1170699965505.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HADOOP-977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arun C Murthy updated HADOOP-977:
---------------------------------

    Attachment: HADOOP-977_20070208_2.patch

Update patch since HADOOP-975 got in...

> The output from the user's task should be tagged and sent to the resepective console streams.
> ---------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-977
>                 URL: https://issues.apache.org/jira/browse/HADOOP-977
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: mapred
>    Affects Versions: 0.11.0
>            Reporter: Owen O'Malley
>         Assigned To: Arun C Murthy
>             Fix For: 0.12.0
>
>         Attachments: HADOOP-977_20070207_1.patch, HADOOP-977_20070208_2.patch
>
>
> Currently, the JobClient prints the combined stdout & stderr to the console. It would be good if the output were tagged with the task id and sent to the stdout or stderr matching where it was sent by the task. So if your Mapper (task_0001_m_000123_0) writes "foobar" to stderr, the submitting user would see "task_0001_m_000123_0: foobar" on their stderr. Clearly this depends on HADOOP-975.

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