You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "leozhang (JIRA)" <ji...@apache.org> on 2018/10/26 02:39:00 UTC
[jira] [Created] (HIVE-20814) New create function between
HiveServer2 is not synchronized
leozhang created HIVE-20814:
-------------------------------
Summary: New create function between HiveServer2 is not synchronized
Key: HIVE-20814
URL: https://issues.apache.org/jira/browse/HIVE-20814
Project: Hive
Issue Type: Improvement
Components: Beeline
Affects Versions: 1.1.0
Reporter: leozhang
Attachments: image-2018-10-26-10-23-48-101.png, image-2018-10-26-10-24-16-669.png, image-2018-10-26-10-24-54-904.png, image-2018-10-26-10-26-00-591.png, image-2018-10-26-10-27-32-291.png
I am using CDH open source version 5.15.0, where the Hive version is 1.1.0.
I have 3 Metastore services and 3 HiveServer2 services in the cluster, Metastore and HiveServer2 don't currently have HA turned on. The cluster opens the Sentry service and configures the Hive Auxiliary JARs Directory attribute.
Now I am having a problem, I am using beeline to connect to HiveServer2 on node 1 to create a function that is successful and can be queried normally. But if I now connect to HiveServer2 of node 2 via Beeline, I can't see the function I just created on node 1 through _show function_. I have to restart HiveServer2 on node 2 to see the function created on node 1 just now.
I don't know the reason and solution for this problem, I hope I can get help, thank you!
exp:
connect dn1.test.com:10000 to create function _zzytest_trans_ , use _show functions_ I can see it
!image-2018-10-26-10-24-16-669.png!
!image-2018-10-26-10-24-54-904.png!
At this point I used beeline to connect to dn4.test.com:10000 and use the show functions command to view the function and I can't find the zzytest_trans function. I have to restart HiveServer2 on the dn4.test.com node to see the zzytest_trans function.
!image-2018-10-26-10-26-00-591.png!
!image-2018-10-26-10-27-32-291.png!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)