[
https://issues.apache.org/jira/browse/PIG-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13808156#comment-13808156
]
Raghu Angadi commented on PIG-3549:
-----------------------------------
awesome! Job url would be even better. Especially with Hadoop2 and Yarn, it is
not as simple as before to go the job history.
> Print hadoop jobids for failed, killed job
> ------------------------------------------
>
> Key: PIG-3549
> URL: https://issues.apache.org/jira/browse/PIG-3549
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.12.0
> Reporter: Aniket Mokashi
> Assignee: Aniket Mokashi
> Fix For: 0.12.1
>
> Attachments: PIG-3549.patch
>
>
> It would be better if we dump the hadoop job ids for failed, killed jobs in
> pig log. Right now, log looks like following-
> {noformat}
> ERROR org.apache.pig.tools.grunt.Grunt: ERROR 6017: Job failed! Error - NA
> INFO
> org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.MapReduceLauncher:
> Job job_pigexec_1 killed
> {noformat}
> From that its hard to say which hadoop job failed if there are multiple jobs
> running in parallel.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
