[
https://issues.apache.org/jira/browse/TEZ-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14961288#comment-14961288
]
Jason Lowe commented on TEZ-2679:
---------------------------------
+1 looks OK to me. This makes the behavior more inline with how MapReduce
worked and will allow admins to set paths without users totally stomping them.
This may require us to do the same sort of whitelist for env appending vs.
replacing like MAPREDUCE-6491 proposes for MapReduce. Not sure if that would
need to be part of this JIRA or a separate one.
> 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
> Attachments: TEZ-2679.1.patch, TEZ-2679.2.patch, TEZ-2679.3.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)
