[
https://issues.apache.org/jira/browse/YARN-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15191384#comment-15191384
]
Gera Shegalov commented on YARN-4789:
-------------------------------------
The patch is throwing an exception only when both the user and the admin
specified an environment variable that cannot be reconciled via concatenation
as it happens with various *PATHs, which is the intent of the option 2.
Following option 1 would replace the user env. But this seemed to me to violate
the spirit of this conf. This conf is designed to preserve the admin settings
while allowing to be overridden by the user. That's why I thought warning both
sides about misconfig is the best course of action here.
> Provide helpful exception for non-PATH-like conflict with admin.user.env
> ------------------------------------------------------------------------
>
> Key: YARN-4789
> URL: https://issues.apache.org/jira/browse/YARN-4789
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.7.2
> Reporter: Gera Shegalov
> Assignee: Gera Shegalov
> Attachments: YARN-4789.001.patch
>
>
> Environment variables specified in mapreduce.admin.user.env are supposed to
> be paths (class, shell, library) and they can be merged with the
> user-provided values. However, it's also possible that the cluster admins
> specify some non-PATH-like variable such as JAVA_HOME. In this case if there
> is the same variable provided by the user, we'll get a concatenation that
> does not make sense and is difficult to debug.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
