hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kengo Seki (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-9642) Configuration to resolve environment variables via ${env.VARIABLE} references
Date Sun, 22 Mar 2015 15:35:11 GMT

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

Kengo Seki updated HADOOP-9642:
-------------------------------
    Attachment: HADOOP-9642.001.patch

Attaching a preliminary patch. Default values are not supported yet.

> 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
>            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)

Mime
View raw message