hadoop-pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Francisoud (JIRA)" <j...@apache.org>
Subject [jira] Commented: (PIG-83) logging abstraction
Date Thu, 31 Jan 2008 10:31:34 GMT

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

Benjamin Francisoud commented on PIG-83:
----------------------------------------

I just started a thread on this subject on the dev mailing list [1] and created a wiki page
[2] to hold the result of the discussion.

Can you have a look and answer in the mail thread, I think mailing list are better for general
discussion.
The jira will then keep track of the patches version, implementation details etc...

I'm working on a patch atm, might be done later today or tomorrow.

[1] http://www.mail-archive.com/pig-dev%40incubator.apache.org/msg00611.html
[2] http://wiki.apache.org/pig/LoggingPolicy

> logging abstraction
> -------------------
>
>                 Key: PIG-83
>                 URL: https://issues.apache.org/jira/browse/PIG-83
>             Project: Pig
>          Issue Type: Wish
>            Reporter: Stefan Groschupf
>
> 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