[jira] [Resolved] (HIVE-6839) Config changes in hive CLI should be propagated to tez configs in Hive

["Rajesh Balamohan (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HIVE-6839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rajesh Balamohan resolved HIVE-6839.
------------------------------------

    Resolution: Invalid

It appears that tez.runtime.io.sort.mb can not be set from CLI.  It gets unset automatically in the job by Tez's MultiStageMRConfToTezTranslator.
 
However, as per CLI's output it would still retain the newer value .  It would be good to print some message from tez, whenever these values are unset.  Since this is not hive related issue, I am closing this ticket as "invalid"

> Config changes in hive CLI should be propagated to tez configs in Hive
> ----------------------------------------------------------------------
>
>                 Key: HIVE-6839
>                 URL: https://issues.apache.org/jira/browse/HIVE-6839
>             Project: Hive
>          Issue Type: Bug
>          Components: Tez
>            Reporter: Rajesh Balamohan
>            Assignee: Rajesh Balamohan
>            Priority: Critical
>
> When "hive.execution.engine=tez" is enabled, hive cli launches a tez session.  But any config changes via "set" command is not propagated to TezSessions.  
> E.g 
> 1. hive --hiveconfig hive.execution.engine=tez
> 2. set tez.runtime.io.sort.mb = 1024;
> 3. set tez.runtime.io.sort.mb (//to verify if the parameter is set)
> 4. Run a hive query and check the app logs.  It would not reflect 1024 for  "tez.runtime.io.sort.mb"



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