[ https://issues.apache.org/jira/browse/PIG-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ashutosh Chauhan updated PIG-1215: ---------------------------------- Attachment: pig-1215.patch With this patch, Job ids will now be printed as: 2010-02-08 13:54:26,441 [main] INFO org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.MapReduceLauncher - HadoopJobId: job_201001051416_2282 We currently wait for ~10 seconds for job tracker to assign the job-ids. Its possible that a busy job-tracker may not assign the job-id within that time. In such cases, Pig will log : 2010-02-08 13:54:26,441 [main] INFO org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.MapReduceLauncher - HadoopJobId: NOT AVAILABLE Note that job may still complete successfully in such cases. Also, these job ids will be printed in order they are submitted to job-tracker. > Make Hadoop jobId more prominent in the client log > -------------------------------------------------- > > Key: PIG-1215 > URL: https://issues.apache.org/jira/browse/PIG-1215 > Project: Pig > Issue Type: Improvement > Reporter: Olga Natkovich > Assignee: Ashutosh Chauhan > Fix For: 0.7.0 > > Attachments: pig-1215.patch > > > This is a request from applications that want to be able to programmatically > parse client logs to find hadoop Ids. > The woould like to see each job id on a separate line in the following format: > hadoopJobId: job_123456789 > They would also like to see the jobs in the order they are executed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.