hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Kimball (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-6420) String-to-String Maps should be embeddable in Configuration
Date Wed, 09 Dec 2009 20:16:18 GMT

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

Aaron Kimball updated HADOOP-6420:

    Attachment: HADOOP-6420.2.patch

Good points in the review. getMap() now handles variable substitution as well as deprecation.

Since getMap() itself takes the "key" to resolve, I have implemented deprecation-resolution
at this level. e.g., "prefix.foo" and "prefix.bar" do not need to be individually deprecated
in favor of "newprefix.foo", "newprefix.bar"; instead, you just deprecate "prefix" for "newprefix"
as if it were a monolithic entity in the configuration, and calls to {{getMap("prefix")}}
will be resolved to look up {{getMap("newprefix")}} instead.

If "newprefix.foo" is further deprecated in favor of "some.other.key", this is *not* resolved
by {{getMap("newprefix")}} or {{getMap("prefix")}}. 

> String-to-String Maps should be embeddable in Configuration
> -----------------------------------------------------------
>                 Key: HADOOP-6420
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6420
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: conf
>            Reporter: Aaron Kimball
>            Assignee: Aaron Kimball
>         Attachments: HADOOP-6420.2.patch, HADOOP-6420.patch
> Per MAPREDUCE-1126, we need to be able to take a map of (key, value) pairs and embed
that inside a Configuration object.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message