You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Aniket Mokashi (JIRA)" <ji...@apache.org> on 2014/05/10 23:59:35 UTC
[jira] [Commented] (PIG-3913) Pig should use job's jobClient
wherever possible (fixes local mode counters)
[ https://issues.apache.org/jira/browse/PIG-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13994005#comment-13994005 ]
Aniket Mokashi commented on PIG-3913:
-------------------------------------
Added a new patch for this.
> Pig should use job's jobClient wherever possible (fixes local mode counters)
> ----------------------------------------------------------------------------
>
> Key: PIG-3913
> URL: https://issues.apache.org/jira/browse/PIG-3913
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.13.0
> Reporter: Aniket Mokashi
> Assignee: Aniket Mokashi
> Fix For: 0.13.0
>
> Attachments: PIG-3913-1.patch, PIG-3913-3.patch, PIG-3913-MRv2.v01.patch
>
>
> MapreduceLauncher initializes a statsJobClient to poll counter information of jobs. This works fine in mapreduce mode but it reports incorrect information in local (auto-local) mode. Pig code should try to use org.apache.hadoop.mapred.jobcontrol.Job's getJobClient api to get handle to jobClient wherever possible. statsJobClient (and wherever its references are passed) should be deprecated.
--
This message was sent by Atlassian JIRA
(v6.2#6252)