You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Kengo Seki (JIRA)" <ji...@apache.org> on 2015/03/22 16:36:11 UTC

[jira] [Assigned] (HADOOP-9642) Configuration to resolve environment variables via ${env.VARIABLE} references

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

Kengo Seki reassigned HADOOP-9642:
----------------------------------

    Assignee: Kengo Seki

> Configuration to resolve environment variables via ${env.VARIABLE} references
> -----------------------------------------------------------------------------
>
>                 Key: HADOOP-9642
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9642
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: conf, scripts
>    Affects Versions: 3.0.0, 2.1.0-beta
>            Reporter: Steve Loughran
>            Assignee: Kengo Seki
>            Priority: Minor
>         Attachments: HADOOP-9642.001.patch
>
>
> We should be able to get env variables from Configuration files, rather than just system properties. I propose using the traditional {{env}} prefix {{${env.PATH}}} to make it immediately clear to people reading a conf file that it's an env variable -and to avoid any confusion with system properties and existing configuration properties.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)