You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Cheolsoo Park (JIRA)" <ji...@apache.org> on 2012/12/11 09:29:24 UTC

[jira] [Commented] (PIG-3073) POUserFunc creating log spam for large scripts

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

Cheolsoo Park commented on PIG-3073:
------------------------------------

Hi Jonathan,

How about simply removing that warning message?
{code}
LOG.warn("jobConf not available. Not tracking UDF timing regardless of user preference.");
{code}
According to the comment for {{UdfContext.getJobConf()}}, {{jobConf}} will be null only if it's called on the front-end. In that case, I don't think that this warning message is particularly helpful after all.
{code}
     * Get the JobConf.  This should only be called on
     * the backend.  It will return null on the frontend.
{code}
Please let me know what you think.

Thanks!

                
> POUserFunc creating log spam for large scripts
> ----------------------------------------------
>
>                 Key: PIG-3073
>                 URL: https://issues.apache.org/jira/browse/PIG-3073
>             Project: Pig
>          Issue Type: Bug
>    Affects Versions: 0.11, 0.12
>            Reporter: Jonathan Coveney
>            Assignee: Jonathan Coveney
>             Fix For: 0.12
>
>         Attachments: PIG-3073-0.patch
>
>
> POUserFunc got some new logging in the case where a JobConf isn't available. In certain cases (huge scripts with tons of UDFs), this is creating gigantic logs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira