[
https://issues.apache.org/jira/browse/HADOOP-9642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318733#comment-17318733
]
Steve Loughran commented on HADOOP-9642:
----------------------------------------
Got a followon to this: HADOOP-17631
if env var access is restricted, I want the resolution of ${env.VAR:-FALLBACK}
to go to evaluation fo the fallback, rather than just return the string
unexpanded. I think this makes sense in the concept of "fallback" -just treat
the var as unset; and it allows you to put in env variable refs into
core-defaults (HADOOP-17386) without worrying about breaking things.
Can anyone see any security implications from such a change? I can't. We'd be
treating all vars as resolving to null, so there's no info leakage about
whether a var is set/unset.
> 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: 2.1.0-beta, 3.0.0-alpha1
> Reporter: Steve Loughran
> Assignee: Kengo Seki
> Priority: Minor
> Fix For: 3.0.0-alpha1
>
> 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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
