[
https://issues.apache.org/jira/browse/TEZ-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Eagles updated TEZ-2679:
---------------------------------
Release Note:
TEZ-2679 introduced new admin configuration (tez.am.launch.cluster-default.env,
tez.task.launch.cluster-default.env) settings. The settings will be merged per
environment variable and environment variables specified in both admin setting
and user override will merged in the following manner (assuming linux classpath
here, but works for other OS's).
./:USER_PATH:ADMIN_PATH
> Admin forms of launch env settings
> ----------------------------------
>
> Key: TEZ-2679
> URL: https://issues.apache.org/jira/browse/TEZ-2679
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Jason Lowe
> Assignee: Jonathan Eagles
> Fix For: 0.7.1, 0.8.2
>
> Attachments: TEZ-2679.1.patch, TEZ-2679.2.patch, TEZ-2679.3.patch,
> TEZ-2679.4.patch
>
>
> Tez should provide corresponding admin configs for launch env and java opt
> settings that can be specified in tez-site.xml by cluster admins. For
> example, if users override the launch env settings to setup LD_LIBRARY_PATH
> to just reference their libs then we can fail to load the native Hadoop libs.
> This is currently mitigated by having Tez rely on the MapReduce admin
> properties in many cases, but Tez should provide its own admin settings to
> match the Tez-specific non-admin settings.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
