Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Mon, 9 Mar 2015 15:23:40 +0000 (UTC)
From: "Allen Wittenauer (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12434511.1251813629000.37875.1425914620072@Atlassian.JIRA>
In-Reply-To: <JIRA.12434511.1251813629000@Atlassian.JIRA>
References: <JIRA.12434511.1251813629000@Atlassian.JIRA>
 <JIRA.12434511.1251813629063@arcas>
Subject: [jira] [Reopened] (HADOOP-6228) Configuration should allow storage
 of null values.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Allen Wittenauer reopened HADOOP-6228:
--------------------------------------

argh wrong jira.

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