[
https://issues.apache.org/jira/browse/PIG-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13958218#comment-13958218
]
Cheolsoo Park commented on PIG-3858:
------------------------------------
[~lbendig], you're right. I've just confirmed that the same problem exists in
tez branch.
I was going to suggest to implement a separate StatusReporter for fetch mode
like PIG-3829 did, but that won't work because of these static calls. Bad,
bad... :( I'd like to avoid having FetchContext and TaskInputOutputContext in
PigStatusReporter, but I don't have a better suggestion.
> PigLogger/PigStatusReporter is not set for fetch tasks
> ------------------------------------------------------
>
> Key: PIG-3858
> URL: https://issues.apache.org/jira/browse/PIG-3858
> Project: Pig
> Issue Type: Bug
> Reporter: Lorand Bendig
> Assignee: Lorand Bendig
> Attachments: PIG-3858.patch
>
>
> PigLogger initialization is missing which leads to NPE if counters are
> accessed during a fetch tasks. Some queries to reproduce this issue:
> 1.
> {code}
> set opt.fetch true;
> A = load ...
> B = foreach A generate TOBAG(TOTUPLE(null));
> dump B;
> {code}
> -> NPE when PigWarning.SKIP_UDF_CALL_FOR_NULL is incremented
> 2.
> {code}
> set opt.fetch true;
> set pig.udf.profile true;
> A = load ...
> B = foreach A generate [any UDF]
> {code}
> -> NPE when POUserFunc.INVOCATION_COUNTER is incremented
--
This message was sent by Atlassian JIRA
(v6.2#6252)
