[
https://issues.apache.org/jira/browse/PIG-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Francisoud updated PIG-83:
-----------------------------------
Attachment: PIG-83-v03.patch
Well anything is better than System.out.println()
Here's a patch to use commons logging everywhere, the previous one became
obsolete because of PIG-32.
This one does the same as patch v01 but take it even further by removing
PigLogger class and use Commons Logging instead.
There is no dependency to log4j at the import level (it only uses commons
logging interfaces)
> 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-83-v03.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.
