You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2017/11/03 16:41:00 UTC
[jira] [Updated] (HADOOP-15015) TestConfigurationFieldsBase to use
SLF4J for logging
[ https://issues.apache.org/jira/browse/HADOOP-15015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran updated HADOOP-15015:
------------------------------------
Assignee: Steve Loughran (was: Bharat Viswanadham)
Status: Patch Available (was: Open)
> TestConfigurationFieldsBase to use SLF4J for logging
> ----------------------------------------------------
>
> Key: HADOOP-15015
> URL: https://issues.apache.org/jira/browse/HADOOP-15015
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf, test
> Affects Versions: 3.0.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Attachments: HADOOP-15015-001.patch
>
>
> {{TestConfigurationFieldsBase}} has a protected "configDebug" field used to turn logging on/off
> {code}
> if (configDebug) {
> System.out.println("Field: " + f);
> }
> {code}
> Presumably its there to allow people with code access to debug their classes. But if we switch to SLF4J you get controllable logging @ runtime.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org