hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9487) Deprecation warnings in Configuration should go to their own log or otherwise be suppressible
Date Thu, 06 Jun 2013 09:23:20 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-9487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13676865#comment-13676865

Steve Loughran commented on HADOOP-9487:

No, I'm proposing a separate Commons Logging logger

First, the classic log
 Log LOG = LogFactory.getLog(Configuration.class);
Now, a new one purely for deprecation
 Log LOG_DEPRECATION = LogFactory.getLog("org.apache.hadoop.conf.Configuration.deprecation");

You log deprecation at info:

 LOG_DEPRECATION.info("mapred.speculative.execution.slowNodeThreshold is deprecated")

Now you can tune deprecation warnings in Log4J

See? No new config options, just tuning log messages via Log4J, which is usuallyy the best
place to do it

> Deprecation warnings in Configuration should go to their own log or otherwise be suppressible
> ---------------------------------------------------------------------------------------------
>                 Key: HADOOP-9487
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9487
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: conf
>    Affects Versions: 3.0.0
>            Reporter: Steve Loughran
> Running local pig jobs triggers large quantities of warnings about deprecated properties
-something I don't care about as I'm not in a position to fix without delving into Pig. 
> I can suppress them by changing the log level, but that can hide other warnings that
may actually matter.
> If there was a special Configuration.deprecated log for all deprecation messages, this
log could be suppressed by people who don't want noisy logs

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message