[
https://issues.apache.org/jira/browse/TEZ-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957410#comment-14957410
]
Jonathan Eagles commented on TEZ-2679:
--------------------------------------
[~hitesh], you are correct there is a small behavior change in that users who
are overriding user env setting and not setting LD_LIBRARY_PATH would get a
different LD_LIBRARY_PATH. Before they would only get './' and now they will
get './' + NATIVE_LIB_PARAM_DEFAULT. I think this is an acceptable behavior
change. If there job was working with the old behavior, likely it will be
working with the new behavior. You are correct that we should call out the
incompatibility. If you are ok with this, I will mark this as an incompatible
change and add a release note about this behavior change.
> 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 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)
