[jira] [Commented] (TEZ-1023) Tez runtime configuration changes by users are not propagated to the jobs

["Siddharth Seth (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TEZ-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13978591#comment-13978591 ] 

Siddharth Seth commented on TEZ-1023:
-------------------------------------

Looks good. One minor change though.
{code}
final String value = (tezValue == null) ? mrValue : tezValue;
{code} followed by a set of the value.
If the tez key is already being used, we should not be setting it again.

> Tez runtime configuration changes by users are not propagated to the jobs
> -------------------------------------------------------------------------
>
>                 Key: TEZ-1023
>                 URL: https://issues.apache.org/jira/browse/TEZ-1023
>             Project: Apache Tez
>          Issue Type: Bug
>    Affects Versions: 0.4.0
>            Reporter: Rajesh Balamohan
>            Assignee: Rajesh Balamohan
>         Attachments: TEZ-1023-v1.patch
>
>
> Currently if a tezsession starts, all tez runtime settings are applicable across the session.  Any changes to tez runtime configs like ("tez.runtime.io.sort.mb", "tez.runtime.shuffle.connect.timeout", "tez.runtime.shuffle.merge.percent" etc) are not propagated to the jobs.  
> Users should be allowed to change tez-runtime configs. (e.g from hive-cli user should be modify to set tez.runtime.io.sort.mb).



--
This message was sent by Atlassian JIRA
(v6.2#6252)