hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phabricator (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-2931) conf settings may be ignored
Date Fri, 13 Apr 2012 00:09:29 GMT

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

Phabricator commented on HIVE-2931:
-----------------------------------

kevinwilfong has commented on the revision "HIVE-2931 [jira] conf settings may be ignored".

  Previously, this is what was effectively done, since every time
   public static Hive get(HiveConf c)
  was called needsRefresh was set to true in which case the thread local Hive instance was
replaced with a new instance using the conf.



REVISION DETAIL
  https://reviews.facebook.net/D2781

                
> conf settings may be ignored
> ----------------------------
>
>                 Key: HIVE-2931
>                 URL: https://issues.apache.org/jira/browse/HIVE-2931
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Namit Jain
>            Assignee: Kevin Wilfong
>         Attachments: HIVE-2931.D2781.1.patch, hive.2931.1.patch
>
>
> This is a pretty serious problem.
> If a conf variable is changed, Hive may not pick up the variable unless the metastore
variables are changed.
> When any session variables are changed, it might be simpler to update the corresponding
Hive conf.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message