[
https://issues.apache.org/jira/browse/PIG-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorand Bendig updated PIG-3888:
-------------------------------
Attachment: PIG-3888.patch
The patch sets the task attempt id and also restores the jobconf at the end of
the fetch task. Thus, the subsequent operators won't be affected by the messed
up jobConf which could otherwise cause wrong initialization issues.
> Direct fetch doesn't differentiate between frontend and backend sides
> ---------------------------------------------------------------------
>
> Key: PIG-3888
> URL: https://issues.apache.org/jira/browse/PIG-3888
> Project: Pig
> Issue Type: Bug
> Reporter: Lorand Bendig
> Assignee: Lorand Bendig
> Attachments: PIG-3888.patch
>
>
> While testing PIG-3558, I found that fetch mode doesn't set the task id in
> the jobconf before running. As a consequence, {{UdfContext#isFrontend()}}
> will always return true. Loaders and Storers which initialize themselves
> based on this flag may fail.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
