[ https://issues.apache.org/jira/browse/HADOOP-9642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14493955#comment-14493955 ]
Hudson commented on HADOOP-9642: -------------------------------- FAILURE: Integrated in Hadoop-Hdfs-trunk #2095 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/2095/]) HADOOP-9642. Configuration to resolve environment variables via ${env.VARIABLE} references (Kengo Seki via aw) (aw: rev d4e8c09593b8edc4d0494d64ce19ac78c6f31277) * hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/conf/TestConfiguration.java * hadoop-common-project/hadoop-common/CHANGES.txt * hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/conf/Configuration.java > 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: New Feature > Components: conf, scripts > Affects Versions: 3.0.0, 2.1.0-beta > Reporter: Steve Loughran > Assignee: Kengo Seki > Priority: Minor > Fix For: 3.0.0 > > Attachments: HADOOP-9642.001.patch, HADOOP-9642.002.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)