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] [Commented] (PIG-2207) Support custom counters for aggregating warnings from different udfs
Date Sun, 02 Feb 2014 05:18:10 GMT

    [ https://issues.apache.org/jira/browse/PIG-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888827#comment-13888827
] 

Cheolsoo Park commented on PIG-2207:
------------------------------------

[~aniket486], do you mind taking a quick look at PIG-3739? It fails after this commit, and
I am not sure whether the test needs to be modified or this patch introduces a bug. Thanks!

> Support custom counters for aggregating warnings from different udfs
> --------------------------------------------------------------------
>
>                 Key: PIG-2207
>                 URL: https://issues.apache.org/jira/browse/PIG-2207
>             Project: Pig
>          Issue Type: Improvement
>            Reporter: Thejas M Nair
>            Assignee: Aniket Mokashi
>              Labels: newbie
>         Attachments: PIG-2207-1.patch, PIG-2207-5.patch
>
>
> Pig allows udfs to aggregate warning messages instead of writing out a separate warning
message each time. Udfs can do this by logging the warning using EvalFunc.warn(String msg,
Enum) call. But the udfs are forced to use PigWarning class if the warning needs to be printed
at the end of the pig script . 
> For example, with the changes in PIG-2191, some of the builtin udfs are using PigWarning.UDF_WARNING_1
as argument in calls to EvalFunc.warn. This will result in the warning count being printed
on STDERR -
> {code}
> 2011-08-05 22:10:29,285 [main] WARN  org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.MapReduceLauncher
- Encountered Warning UDF_WARNING_1 2 time(s).
> 2011-08-05 22:10:29,285 [main] INFO  org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.MapReduceLauncher
- Success!
> {code}
> But it would be better if a udf such as the LOWER udf could use a custom warning counter,
and the STDERR is like -
> {code}
> 2011-08-05 22:10:29,285 [main] WARN  org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.MapReduceLauncher
- Encountered Warning LOWER_FUNC_INPUT_WARNING 2 time(s).
> 2011-08-05 22:10:29,285 [main] INFO  org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.MapReduceLauncher
- Success!
> {code}
> A new function could be added to support this - (something like) EvalFunc.warn(String
warnName, String warnMsg);  A specific counter group could be used for udf warnings (see org.apache.hadoop.mapred.Counters),
and counters for that group could be done during final warning aggregation in done in MapReduceLauncher.computeWarningAggregate().




--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message