hadoop-pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thejas M Nair (JIRA)" <j...@apache.org>
Subject [jira] Commented: (PIG-1570) native mapreduce operator MR job does not follow same failure handling logic as other pig MR jobs
Date Mon, 30 Aug 2010 17:29:54 GMT

    [ https://issues.apache.org/jira/browse/PIG-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904263#action_12904263
] 

Thejas M Nair commented on PIG-1570:
------------------------------------

The code path that is followed in case of the native MR job is still different because the
jar is a black box, and pig just calls the main function, pig doesn't even know if it is a
MR job that is actually being run.
This fixes the pig stats reporting (log messages) for failed native MR job and also the feature
list in the native MR job.


> native mapreduce operator MR job does not follow same failure handling logic as other
pig MR jobs
> -------------------------------------------------------------------------------------------------
>
>                 Key: PIG-1570
>                 URL: https://issues.apache.org/jira/browse/PIG-1570
>             Project: Pig
>          Issue Type: Bug
>            Reporter: Thejas M Nair
>            Assignee: Thejas M Nair
>             Fix For: 0.8.0
>
>         Attachments: PIG-1570.1.patch
>
>
> The code path for handling failure in MR job corresponding to native MR is different
and does not have the same behavior.
> For example, even if the MR job for mapreduce operator fails, the number of jobs that
failed is being reported as 0 in PigStats log.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message