[
https://issues.apache.org/jira/browse/TEZ-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980908#comment-14980908
]
Hitesh Shah commented on TEZ-2679:
----------------------------------
I think we may need to file an INFRA jira for that. Would you mind filing that?
FWIW, [~jeagles] you are a Tez JIRA admin too so both of us have the same level
of permissions. In any case, a more descriptive message in CHANGES.txt should
suffice for now.
> 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)
