Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Tue, 30 Oct 2012 04:40:12 +0000 (UTC)
From: "Harsh J (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <641283874.42764.1351572012973.JavaMail.jiratomcat@arcas>
In-Reply-To: <432316238.41275.1351549154756.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (HADOOP-8995) Remove unnecessary bogus exception
 log from Configuration
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Harsh J commented on HADOOP-8995:
---------------------------------

Just to clarify, these were not _bogus_ but helpers in identifying what classes instantiated the Configuration object (prints a trace).

Has not come helpful to me personally, but was a good thing to have (just in case). Perhaps we could have just lowered its level below DEBUG, such as TRACE.
                
> Remove unnecessary bogus exception log from Configuration
> ---------------------------------------------------------
>
>                 Key: HADOOP-8995
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8995
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>            Reporter: Jing Zhao
>            Assignee: Jing Zhao
>            Priority: Minor
>             Fix For: 1.2.0
>
>         Attachments: Hadoop.8995.b1.001.patch
>
>
> In Configuration#Configuration(boolean) and Configuration#Configuration(Configuration), bogus exceptions are thrown when Log level is DEBUG.

--
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