hadoop-common-issues mailing list archives

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

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

Steve Loughran commented on HADOOP-6228:

# Yes, {{<value></value>}}  is effectively the empty string, at least for string
values. I guess it gets complex with integers. 
# There's also that trailing whitespace problem, is {{<value>
</value> }} == "" too?
# Nullness is a very strange thing to deal with in text formats; empty strings are simpler.
Those things that look for a script could say "script name == empty string => skip". 
# Processing integers is harder. If you do a Conf.getInt(key, 10), and Configuration.get(key)
returns "" over null, does that mean you want the default, or null?

Either way, this is quite a big change in the configuration side of things.

> 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