hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Wang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-13699) Configuration does not substitute multiple references to the same var
Date Fri, 07 Oct 2016 23:10:20 GMT

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

Andrew Wang updated HADOOP-13699:
    Attachment: HADOOP-13699.001.patch

Patch attached. This only attempts to catch the simple case of a variable resolving to itself.
Support for detecting multiple variable loops is removed.

Solving this generally is like detecting a loop in a linked list. Since this is performance
sensitive code, I think we'd rather not do that.

> Configuration does not substitute multiple references to the same var
> ---------------------------------------------------------------------
>                 Key: HADOOP-13699
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13699
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>    Affects Versions: 3.0.0-alpha1
>            Reporter: Andrew Wang
>            Assignee: Andrew Wang
>            Priority: Critical
>         Attachments: HADOOP-13699.001.patch
> Config var loop detection was originally introduced by HADOOP-6871. Due to cycle detection
changes in the trunk patch for HADOOP-11506, resolution for multiple references to the same
variable no longer resolved, e.g.
> {noformat}
> somekey = "${otherkey} ${otherkey}"
> {noformat}
> This loop detection business is fragile, expensive, and not in branch-2, so let's reduce

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message