hive-dev mailing list archives

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


Phabricator commented on HIVE-2931:

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

  One thing I just don't understand is, if always doing db.conf= c works, then why we need
to comparing the meta vars and only modify when there is difference? I think we must have
missed something here.


> conf settings may be ignored
> ----------------------------
>                 Key: HIVE-2931
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


View raw message