[
https://issues.apache.org/jira/browse/PIG-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757310#action_12757310
]
Dmitriy V. Ryaboy commented on PIG-948:
---------------------------------------
I don't see a problem with url construction in Pig code. If Hadoop exposed
this, then sure, it would be better to use such a feature.
Since Hadoop does not expose it (afaik), it's more useful for the end-user to
have this url than to have a jobid. Maintenance on this piece of code is
minimal -- after all, it's just a simple string concatenation we are talking
about. If Hadoop changes how this url is constructed, it will take about 3
minutes to fix, 2.5 of which will be spent opening a Jira ticket.
In the meantime, users will have a more usable product than they would without
this one line of code.
> [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.
