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/09 16:23:39 UTC

[jira] [Resolved] (HADOOP-6228) Configuration should allow storage of null values.

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

Allen Wittenauer resolved HADOOP-6228.
--------------------------------------
    Resolution: Duplicate

Closing as a dupe since the other jira has code attached.

> Configuration should allow storage of null values.
> --------------------------------------------------
>
>                 Key: HADOOP-6228
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6228
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>            Reporter: Hemanth Yamijala
>
> Currently the configuration class does not allow null keys and values. Null keys don't make sense, but null values may have semantic meaning for some features. Not storing these values in configuration causes some arguable side effects. For instance, if a value is defined in defaults, but wants to be disabled in site configuration by setting it to null, there's no way to do this currently. Also, no track of keys with null values is recorded. Hence, tools like dump configuration (HADOOP-6184) would not display these properties.
> Does this seem like a sensible use case ?



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