[PIG-3860] Refactor PigStatusReporter and PigLogger for non-MR execution engine

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: tez-branch, 0.13.0
• Assignee: Cheolsoo Park
• Reporter: Cheolsoo Park
• Created: 02/Apr/14 21:51
• Updated: 07/Jul/14 18:08
• Resolved: 28/Apr/14 22:03

Description

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-

SET opt.fetch false;
SET pig.udf.profile true;
a = LOAD 'foo' AS (x:chararray);
b = FOREACH a GENERATE LOWER(x);
DUMP b;

The problem is that PigStatusReport.getInstance().getCounter() returns null since TezStatusReporter is used in Tez.

PigStatusReporter.getInstance().getCounter(counterGroup, INVOCATION_COUNTER).increment(TIMING_FREQ);

Issue Links

• is related to: PIG-3829 Make custom counter work
• relates to: PIG-3858 PigLogger/PigStatusReporter is not set for fetch tasks