You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (Jira)" <ji...@apache.org> on 2021/04/09 13:37:00 UTC

[jira] [Created] (HADOOP-17631) Configuration ${env.VAR:-FALLBACK} eval should extract/eval FALLBACK restrictSystemProps=true

Steve Loughran created HADOOP-17631:
---------------------------------------

             Summary: Configuration ${env.VAR:-FALLBACK} eval should extract/eval FALLBACK restrictSystemProps=true 
                 Key: HADOOP-17631
                 URL: https://issues.apache.org/jira/browse/HADOOP-17631
             Project: Hadoop Common
          Issue Type: Bug
          Components: common
    Affects Versions: 3.3.0
            Reporter: Steve Loughran


When configuration reads in resources with a restricted parser, it skips evaluaging system ${env. } vars. But it also skips evaluating fallbacks

As a result, a property like

${env.LOCAL_DIRS:-${hadoop.tmp.dir}} ends up evaluating as ${env.LOCAL_DIRS:-${hadoop.tmp.dir}}

It should instead fall back to the "env var unset" option of ${hadoop.tmp.dir}. This allows for configs (like for s3a buffer dirs) which are usable in restricted mode as well as unrestricted deployments.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org