hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6228) Configuration should allow storage of null values.
Date Tue, 01 Sep 2009 16:16:32 GMT

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

Hemanth Yamijala commented on HADOOP-6228:

bq. Which situations are in there that you can't just get away with an empty string instead?

Steve, this may work as well. But currently if there's no value defined for a property (i.e.
we have something like <value></value> in the config file), this is returned as
null, and not as empty string. I suppose this can be changed though ? Is that what you are
saying we can do ?

> 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 is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message