pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aniket Mokashi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PIG-3913) Pig should use job's jobClient wherever possible (fixes local mode counters)
Date Tue, 20 May 2014 17:46:41 GMT

     [ https://issues.apache.org/jira/browse/PIG-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Aniket Mokashi updated PIG-3913:
--------------------------------

    Attachment:     (was: PIG-3913-7.patch)

> 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-5.patch, PIG-3913-6.patch,
PIG-3913-7.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)

Mime
View raw message