pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cheolsoo Park (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PIG-3860) Refactor PigStatusReporter and PigLogger for non-MR execution engine
Date Mon, 28 Apr 2014 21:39:16 GMT

     [ https://issues.apache.org/jira/browse/PIG-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Cheolsoo Park updated PIG-3860:
-------------------------------

    Attachment: PIG-3860-2-tez.patch
                PIG-3860-2-trunk.patch

Update patches incorporating Daniel's comment.

> Refactor PigStatusReporter and PigLogger for non-MR execution engine
> --------------------------------------------------------------------
>
>                 Key: PIG-3860
>                 URL: https://issues.apache.org/jira/browse/PIG-3860
>             Project: Pig
>          Issue Type: Bug
>            Reporter: Cheolsoo Park
>            Assignee: Cheolsoo Park
>             Fix For: tez-branch, 0.13.0
>
>         Attachments: PIG-3860-1-tez.patch, PIG-3860-1-trunk.patch, PIG-3860-2-tez.patch,
PIG-3860-2-trunk.patch
>
>
> 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)

Mime
View raw message