[
https://issues.apache.org/jira/browse/TEZ-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14044237#comment-14044237
]
Hitesh Shah commented on TEZ-1127:
----------------------------------
bq. The PWD is being set in the code. Thats because there we can rely on the NM
setting an explicit PWD env var that we can rely on. I am using the same value
as the once currently configured and used by us via
MRJobConfig.DEFAULT_MAPRED_ADMIN_USER_ENV. We can follow up in a different jira
if this should be changed.
This seems fine. If the hadoop lib native path is questionable, how about we
just set PWD via code and not have a default env setting.
Still worried a bit about the AM_JAVA_OPTS - should be called out very clearly
in the incompatible changes section.
Assuming above is addressed, patch should be fine to commit.
> Add TEZ_TASK_JAVA_OPTS and TEZ_ENV configs to specify values from config
> ------------------------------------------------------------------------
>
> Key: TEZ-1127
> URL: https://issues.apache.org/jira/browse/TEZ-1127
> Project: Apache Tez
> Issue Type: Sub-task
> Affects Versions: 0.4.0
> Reporter: Pala M Muthaia
> Assignee: Bikas Saha
> Attachments: TEZ-1127.1.patch
>
>
> There is no global setting available to specify JVM parameters for tez tasks
> (e.g: specifying native library location with java.library.path). Yarn allows
> specifying application.classpath, but not java opts. The only option right
> now is to set mapreduce.map.java.opts in the tez job config (or
> hive.tez.java.opts for Hive on Tez).
> Suggestion from Bikas, while discussing this in tez-user group, is tez should
> have "TEZ_TASK_JAVA_OPTS so that you don’t have to specify this via mapreduce
> configuration parameters"
--
This message was sent by Atlassian JIRA
(v6.2#6252)
