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 "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2015/03/28 03:10:52 UTC

[jira] [Updated] (HADOOP-8698) Do not call unneceseary setConf(null) in Configured constructor

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

Allen Wittenauer updated HADOOP-8698:
-------------------------------------
    Fix Version/s:     (was: 3.0.0)
                       (was: 0.24.0)

> Do not call unneceseary setConf(null) in Configured constructor
> ---------------------------------------------------------------
>
>                 Key: HADOOP-8698
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8698
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>    Affects Versions: 0.23.3, 3.0.0
>            Reporter: Radim Kolar
>            Assignee: Radim Kolar
>            Priority: Minor
>         Attachments: setconf-null.txt, setconf-null2.txt, setconf-null3.txt, setconf-null4.txt
>
>
> no-arg constructor of /org/apache/hadoop/conf/Configured calls setConf(null). This is unnecessary and it increases complexity of setConf() code because you have to check for not null object reference before using it. Under normal conditions setConf() is never called with null reference, so not null check is unnecessary.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)