[prev in list] [next in list] [prev in thread] [next in thread] 

List:       hadoop-dev
Subject:    [jira] [Resolved] (HADOOP-1078) Improve logging
From:       "Harsh J (Resolved) (JIRA)" <jira () apache ! org>
Date:       2011-12-29 6:36:31
Message-ID: 1009715388.50694.1325140591058.JavaMail.tomcat () hel ! zones ! apache ! org
[Download RAW message or body]


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

Harsh J resolved HADOOP-1078.
-----------------------------

    Resolution: Not A Problem

I think we've long since switched over to using the .class attribute. Resolving as \
not a problem anymore.  
> Improve logging
> ---------------
> 
> Key: HADOOP-1078
> URL: https://issues.apache.org/jira/browse/HADOOP-1078
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Philippe Gassmann
> 
> Loggers in hadoop are created using LogFactory.getLog("some package styled \
> things");  This is very confusing since the string specified in getLog() sometime \
> is the class name sometime not. (eg : the class org.apache.hadoop.mapred.Task \
> contains a logger created by \
> LogFactory.getLog("org.apache.hadoop.mapred.TaskRunner"); which is very confusing) \
> I think that logger should be always created using  \
> LogFactory.getLog(MyClass.class); and that if a class needs a logger, then a \
> specific logger must be crated for that class (ie: loggers are private).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: \
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more \
information on JIRA, see: http://www.atlassian.com/software/jira

        


[prev in list] [next in list] [prev in thread] [next in thread]