[
https://issues.apache.org/jira/browse/TEZ-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957624#comment-14957624
]
Jason Lowe commented on TEZ-2679:
---------------------------------
bq. Before they would only get './' and now they will get './' +
NATIVE_LIB_PARAM_DEFAULT.
Actually I don't believe that's the case. The problem is that the cluster env
settings do not append to the user env settings because we're calling
setEnvIfAbsentFromInputString. I think we need to be calling
appendToEnvFromInputString, otherwise users who override LD_LIBRARY_PATH just
to pick up their specific .so will end up accidentally eclipsing the cluster
settings to pick up native codecs and other support from things like
libhadoop.so.
> 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)
