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

Pradeep Kamath commented on PIG-948:
------------------------------------

In my opinion, pig should only print the jobid. Users of pig would most likely 
already be using the hadoop job UI and should be able to track down the job 
given the job id. Giving the job id I think achieves the original issue of 
relating pig script to the corresponding MR jobs. While constructing the url is 
not complicated, embedding it in pig code seems ugly since we will most likely 
not track the changes in this url until a user notices it is broken - giving 
just the  job id is useful in itself I think.

> [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.

Reply via email to