[
https://issues.apache.org/jira/browse/HADOOP-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14353198#comment-14353198
]
Ray Chiang commented on HADOOP-6228:
------------------------------------
HADOOP-11399 adds Configuration#setAllowNullValueProperties() for testing
purposes, specifically for *Config* class static Strings to xml comparison
(e.g. YARN-2957). Just FYI in case someone wants to take the logic and run
with it as far as fixing all the Configuration accessors for null values.
> 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)
