[
https://issues.apache.org/jira/browse/HIVE-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253012#comment-13253012
]
Phabricator commented on HIVE-2931:
-----------------------------------
kevinwilfong has commented on the revision "HIVE-2931 [jira] conf settings may
be ignored".
The reason for comparing the metavars is to determine whether or not a new
metastore client needs to be created or not, once the metastore client is
created, the conf is not updated. So if any of the conf variables used by the
metastore are modified the metastore client needs to be restarted to get those
new configs. I assume this is expensive.
If a config variable is changed which may be accessed by the Hive object, but
not the metastore config variable, if that is changed, there is no need to
create a new metastore client, but Hive's config should still be updated to
make sure it gets the new value.
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
