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 "Owen O'Malley (JIRA)" <ji...@apache.org> on 2007/02/05 19:26:05 UTC
[jira] Created: (HADOOP-977) The output from the user's task should
be tagged and sent to the resepective console streams.
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
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". 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.
[jira] Commented: (HADOOP-977) The output from the user's task
should be tagged and sent to the resepective console streams.
Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471512 ]
Owen O'Malley commented on HADOOP-977:
--------------------------------------
+1
> 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.
[jira] Updated: (HADOOP-977) The output from the user's task should
be tagged and sent to the resepective console streams.
Posted by "Arun C Murthy (JIRA)" <ji...@apache.org>.
[ 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_20070207_1.patch
Patch attached. This, of course, depends on HADOOP-975 and I'll put up another one once that is committed if there are issues...
It uses the enhancements to tasklog.jsp made in HADOOP-975 to fetch stdout and stderr and tags and sends them out to the JobClient's respective streams.
> 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
>
>
> 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.
[jira] Updated: (HADOOP-977) The output from the user's task should
be tagged and sent to the resepective console streams.
Posted by "Arun C Murthy (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (HADOOP-977) The output from the user's task should
be tagged and sent to the resepective console streams.
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doug Cutting updated HADOOP-977:
--------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
I just committed this. Thanks, Arun!
> 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.
[jira] Updated: (HADOOP-977) The output from the user's task should
be tagged and sent to the resepective console streams.
Posted by "Arun C Murthy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arun C Murthy updated HADOOP-977:
---------------------------------
Status: Patch Available (was: Open)
> 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
>
>
> 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.
[jira] Commented: (HADOOP-977) The output from the user's task
should be tagged and sent to the resepective console streams.
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470731 ]
Hadoop QA commented on HADOOP-977:
----------------------------------
+1, because http://issues.apache.org/jira/secure/attachment/12350484/HADOOP-977_20070207_1.patch applied and successfully tested against trunk revision r503864.
> 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
>
>
> 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.
[jira] Updated: (HADOOP-977) The output from the user's task should
be tagged and sent to the resepective console streams.
Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Owen O'Malley updated HADOOP-977:
---------------------------------
Description: 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. (was: 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". Clearly this depends on HADOOP-975.)
> 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
>
>
> 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.