[
https://issues.apache.org/jira/browse/PIG-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13958478#comment-13958478
]
Cheolsoo Park commented on PIG-3860:
------------------------------------
[~daijy], no worries. :-)
In fact, Lorand and I were discussion the exactly same problem in PIG-3858. We
might end up putting TaskInputOutputContext, TezProcessorContext, and
FetchContext in PigStatusReporter. I was wondering whether this is a better way
to fix this.
> PigStatusReporter.getInstance().getCounter() returns null in Tez mode
> ---------------------------------------------------------------------
>
> Key: PIG-3860
> URL: https://issues.apache.org/jira/browse/PIG-3860
> Project: Pig
> Issue Type: Sub-task
> Components: tez
> Affects Versions: tez-branch
> Reporter: Cheolsoo Park
> Assignee: Cheolsoo Park
> Fix For: tez-branch
>
>
> PIG-3829 handles some cases, but NPE can be still thrown for custom counters
> in Tez mode. For example, the following query fails with NPE-
> {code}
> SET opt.fetch false;
> SET pig.udf.profile true;
> a = LOAD 'foo' AS (x:chararray);
> b = FOREACH a GENERATE LOWER(x);
> DUMP b;
> {code}
> The problem is that PigStatusReport.getInstance().getCounter() returns null
> since TezStatusReporter is used in Tez.
> {code}
> PigStatusReporter.getInstance().getCounter(counterGroup,
> INVOCATION_COUNTER).increment(TIMING_FREQ);
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
