[
https://issues.apache.org/jira/browse/HADOOP-9642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13683424#comment-13683424
]
Steve Loughran commented on HADOOP-9642:
----------------------------------------
I'm thinking of the specific use case of resolving values passed down via YARN.
I don't see why we'd need default values, given they aren't there for system
property resolution either.
I agree it's nondeterministic -but again, we have that problem with system
properties
> 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
> Affects Versions: 3.0.0, 2.1.0-beta
> Reporter: Steve Loughran
> Priority: Minor
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
