hadoop-pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Groschupf (JIRA)" <j...@apache.org>
Subject [jira] Commented: (PIG-83) logging abstraction
Date Thu, 07 Feb 2008 18:11:08 GMT

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

Stefan Groschupf commented on PIG-83:
-------------------------------------

Hi, 
sorry to say but from my experience within the last year java.util logging is a pain for serious
production systems. 
We also should learn from the hadoop folks. They had a very long discussion about this topic
and did use java.util logging in the first step but finally moved to log4j.
Pig might should not do the same mistake again. 



> logging abstraction
> -------------------
>
>                 Key: PIG-83
>                 URL: https://issues.apache.org/jira/browse/PIG-83
>             Project: Pig
>          Issue Type: Wish
>            Reporter: Stefan Groschupf
>         Attachments: log4j.properties, logging.properties, PIG-83-v01.patch, PIG-83-v02.patch
>
>
> Pig is logging quite a lot into System.out or System.err. Using a embedded pig in a production
environment requires a logging abstraction like log4j, commons logging, slf4j or something
like that. 
> I would be happy to work on a patch if we decide what would be the best choice. Hadoop
uses log4j.
> Thanks.
> Stefan

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message