You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Namit Jain (Created) (JIRA)" <ji...@apache.org> on 2012/04/06 20:49:23 UTC
[jira] [Created] (HIVE-2931) conf settings may be ignored
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
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
[jira] [Commented] (HIVE-2931) conf settings may be ignored
Posted by "Siying Dong (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253096#comment-13253096 ]
Siying Dong commented on HIVE-2931:
-----------------------------------
+1, will commit after tests pass.
> 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
[jira] [Updated] (HIVE-2931) conf settings may be ignored
Posted by "Carl Steinbach (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carl Steinbach updated HIVE-2931:
---------------------------------
Resolution: Duplicate
Status: Resolved (was: Patch Available)
> 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
[jira] [Commented] (HIVE-2931) conf settings may be ignored
Posted by "Siying Dong (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253525#comment-13253525 ]
Siying Dong commented on HIVE-2931:
-----------------------------------
OK.
> 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
[jira] [Commented] (HIVE-2931) conf settings may be ignored
Posted by "Siying Dong (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253097#comment-13253097 ]
Siying Dong commented on HIVE-2931:
-----------------------------------
+1, will commit after tests pass.
> 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
[jira] [Assigned] (HIVE-2931) conf settings may be ignored
Posted by "Kevin Wilfong (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Wilfong reassigned HIVE-2931:
-----------------------------------
Assignee: Kevin Wilfong (was: Namit Jain)
> 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
[jira] [Commented] (HIVE-2931) conf settings may be ignored
Posted by "Carl Steinbach (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253155#comment-13253155 ]
Carl Steinbach commented on HIVE-2931:
--------------------------------------
This ticket is a duplicate of HIVE-2918. I have provided a patch for HIVE-2918 which provides the same fix along with two new testcases that verify the behavior of hive.exec.max.dynamic.partitions. Please test and commit that patch instead.
> 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
[jira] [Updated] (HIVE-2931) conf settings may be ignored
Posted by "Phabricator (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Phabricator updated HIVE-2931:
------------------------------
Attachment: HIVE-2931.D2781.1.patch
kevinwilfong requested code review of "HIVE-2931 [jira] conf settings may be ignored".
Reviewers: JIRA
https://issues.apache.org/jira/browse/HIVE-2931
Unfortunately, Namit's patch did not pass the tests and he is away. I offer this patch as a different solution. The issue is that before HIVE-2716, Hive would alway have its needsRefresh set to true. Now, however, this is no longer the case. This exposed the issue that the Hive class uses config variables which are not metavariables. This seems perfectly reasonable, except that its HiveConf instance is only updated if a metavariable changes. It should be updated regardless. A metavariable changing should only determine if it needs to connect to a new metastore instance.
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.
TEST PLAN
EMPTY
REVISION DETAIL
https://reviews.facebook.net/D2781
AFFECTED FILES
ql/src/java/org/apache/hadoop/hive/ql/metadata/Hive.java
MANAGE HERALD DIFFERENTIAL RULES
https://reviews.facebook.net/herald/view/differential/
WHY DID I GET THIS EMAIL?
https://reviews.facebook.net/herald/transcript/6309/
Tip: use the X-Herald-Rules header to filter Herald messages in your client.
> 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: Namit Jain
> 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
[jira] [Commented] (HIVE-2931) conf settings may be ignored
Posted by "Carl Steinbach (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253158#comment-13253158 ]
Carl Steinbach commented on HIVE-2931:
--------------------------------------
Also, this patch doesn't add any tests to verify that it actually fixes the problem. Please either add tests or commit HIVE-2918 instead.
> 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
[jira] [Commented] (HIVE-2931) conf settings may be ignored
Posted by "Kevin Wilfong (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253174#comment-13253174 ]
Kevin Wilfong commented on HIVE-2931:
-------------------------------------
I'd prefer to use your patch because, as you said, it is nearly an identical fix, and it has test cases.
> 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
[jira] [Commented] (HIVE-2931) conf settings may be ignored
Posted by "Phabricator (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252995#comment-13252995 ]
Phabricator commented on HIVE-2931:
-----------------------------------
stuart983 has commented on the revision "HIVE-2931 [jira] conf settings may be ignored".
I'm not sure it is the right thing to do. This patch implies that, every time we call Hive.get(HiveConf), we replace the threadlocal Hive object's conf to the one passed in?
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
[jira] [Commented] (HIVE-2931) conf settings may be ignored
Posted by "Phabricator (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253008#comment-13253008 ]
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.
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
[jira] [Updated] (HIVE-2931) conf settings may be ignored
Posted by "Namit Jain (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Namit Jain updated HIVE-2931:
-----------------------------
Status: Patch Available (was: Open)
> 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: Namit Jain
> Attachments: 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
[jira] [Commented] (HIVE-2931) conf settings may be ignored
Posted by "Phabricator (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (HIVE-2931) conf settings may be ignored
Posted by "Phabricator (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (HIVE-2931) conf settings may be ignored
Posted by "Phabricator (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253043#comment-13253043 ]
Phabricator commented on HIVE-2931:
-----------------------------------
stuart983 has accepted the revision "HIVE-2931 [jira] conf settings may be ignored".
Communicated offline with Kevin. It looks fine for now. But I still think fixing setProcessor to update local Hive object is something we still need to do. Maybe we should create a follow-up task for that.
REVISION DETAIL
https://reviews.facebook.net/D2781
BRANCH
svn
> 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
[jira] [Assigned] (HIVE-2931) conf settings may be ignored
Posted by "Namit Jain (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Namit Jain reassigned HIVE-2931:
--------------------------------
Assignee: Namit Jain
> 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: Namit Jain
>
> 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
[jira] [Commented] (HIVE-2931) conf settings may be ignored
Posted by "Namit Jain (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248643#comment-13248643 ]
Namit Jain commented on HIVE-2931:
----------------------------------
https://reviews.facebook.net/differential/diff/8583/
> 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: Namit Jain
>
> 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
[jira] [Updated] (HIVE-2931) conf settings may be ignored
Posted by "Namit Jain (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Namit Jain updated HIVE-2931:
-----------------------------
Attachment: hive.2931.1.patch
> 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: Namit Jain
> Attachments: 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