You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Alan Gates (JIRA)" <ji...@apache.org> on 2008/02/12 22:27:07 UTC

[jira] Resolved: (PIG-83) logging abstraction

     [ https://issues.apache.org/jira/browse/PIG-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alan Gates resolved PIG-83.
---------------------------

       Resolution: Fixed
    Fix Version/s: 0.1.0

Applied the latest patch using logging commons (PIG-83-v03.patch), revision 627115.  Thanks Benjamin.

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


Re: [jira] Resolved: (PIG-83) logging abstraction

Posted by Alan Gates <ga...@yahoo-inc.com>.
Thanks for doing the logging changes.  I'd wanted to get the println()s 
changed to log statements for a while.

Alan.

Benjamin Francisoud wrote:
> Thanks Alan for PIG-83 and PIG-92, it's always pleasant to open my 
> mail box and discover 2 patches where integrated :-)
>
> -- 
> Benjamin Francisoud
>
> Alan Gates (JIRA) a écrit :
>>      [ 
>> https://issues.apache.org/jira/browse/PIG-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel 
>> ]
>>
>> Alan Gates resolved PIG-83.
>> ---------------------------
>>
>>        Resolution: Fixed
>>     Fix Version/s: 0.1.0
>>
>> Applied the latest patch using logging commons (PIG-83-v03.patch), 
>> revision 627115.  Thanks Benjamin.
>>
>>  
>>> logging abstraction
>>> -------------------
>>>
>>>                 Key: PIG-83
>>>                 URL: https://issues.apache.org/jira/browse/PIG-83
>>>             Project: Pig
>>>          Issue Type: Wish
>>>            Reporter: Stefan Groschupf
>>>             Fix For: 0.1.0
>>>
>>>         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
>>>     
>>
>>   
>

Re: [jira] Resolved: (PIG-83) logging abstraction

Posted by Benjamin Francisoud <be...@joost.com>.
Thanks Alan for PIG-83 and PIG-92, it's always pleasant to open my mail 
box and discover 2 patches where integrated :-)

--
Benjamin Francisoud

Alan Gates (JIRA) a écrit :
>      [ https://issues.apache.org/jira/browse/PIG-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Alan Gates resolved PIG-83.
> ---------------------------
>
>        Resolution: Fixed
>     Fix Version/s: 0.1.0
>
> Applied the latest patch using logging commons (PIG-83-v03.patch), revision 627115.  Thanks Benjamin.
>
>   
>> logging abstraction
>> -------------------
>>
>>                 Key: PIG-83
>>                 URL: https://issues.apache.org/jira/browse/PIG-83
>>             Project: Pig
>>          Issue Type: Wish
>>            Reporter: Stefan Groschupf
>>             Fix For: 0.1.0
>>
>>         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
>>     
>
>