Mailing-List: contact pig-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: pig-dev@hadoop.apache.org
Message-ID: <1932320367.1253299156803.JavaMail.jira@brutus>
Date: Fri, 18 Sep 2009 11:39:16 -0700 (PDT)
From: "Daniel Dai (JIRA)" <jira@apache.org>
To: pig-dev@hadoop.apache.org
Subject: [jira] Commented: (PIG-948) [Usability] Relating pig script with MR
 jobs
In-Reply-To: <1102867507.1252359537587.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/PIG-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757330#action_12757330 ] 

Daniel Dai commented on PIG-948:
--------------------------------

If Hadoop expose it, then there is no problem to include. But I don't think Hadoop expose this construction. I agree it is minimal to maintain and useful to many users. What I concern is to put undocumented Hadoop features into Pig code. I do not object to that, but I feel I need more inputs because we break a convention.

How does other developers feel?

> [Usability] Relating pig script with MR jobs
> --------------------------------------------
>
>                 Key: PIG-948
>                 URL: https://issues.apache.org/jira/browse/PIG-948
>             Project: Pig
>          Issue Type: Improvement
>          Components: impl
>            Reporter: Ashutosh Chauhan
>            Assignee: Ashutosh Chauhan
>            Priority: Minor
>         Attachments: pig-948.patch
>
>
> Currently its hard to find a way to relate pig script with specific MR job. In a loaded cluster with multiple simultaneous job submissions, its not easy to figure out which specific MR jobs were launched for a given pig script. If Pig can provide this info, it will be useful to debug and monitor the jobs resulting from a pig script.
> At the very least, Pig should be able to provide user the following information
> 1) Job id of the launched job.
> 2) Complete web url of jobtracker running this job. 

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