[
https://issues.apache.org/jira/browse/HADOOP-9642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14375048#comment-14375048
]
Hadoop QA commented on HADOOP-9642:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12706394/HADOOP-9642.001.patch
against trunk revision 4cd54d9.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5983//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5983//console
This message is automatically generated.
> 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)
