[jira] Commented: (HIVE-210) Refactor HiveConf variables into two categories (global and session level) so that sharing HiveConf object across multiple sessions becomes easier

["Joydeep Sen Sarma (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HIVE-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662855#action_12662855 ] 

Joydeep Sen Sarma commented on HIVE-210:
----------------------------------------

i presume u are asking to distinguishing variables that are 'query' specific versus those that are session level.

if so - the wording of the jira is very confusing. (don't see the point of sharing variables across sessions (except by inheriting initial values from same properties file (as today)).

> Refactor HiveConf variables into two categories (global and session level) so that sharing HiveConf object across multiple sessions becomes easier
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-210
>                 URL: https://issues.apache.org/jira/browse/HIVE-210
>             Project: Hadoop Hive
>          Issue Type: Improvement
>          Components: Clients
>            Reporter: Prasad Chakka
>
> Created while fixing HIVE-84.
> There are lot of variables in HiveConf object that server dual purposes: valid only for a job (job name, id etc) and valid across sessions and jobs. So it may be good idea to separate these so that changes in HiveConf object can be detected and acted appropriately.
> I suppose this requites a sizable refactoring of the code in SessionState, HiveConf & Hive classes. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.