[IMPALA-8974] Create kudu table failed when catalogd connected to mysql directly instead of use HMS

• Type: Bug
• Status: Open
• Priority: Critical
• Resolution: Unresolved
• Affects Version/s: Impala 3.3.0
• Component/s: Frontend
• Environment: Distributor ID: Debian ; Description: Debian GNU/Linux 8.6 (jessie) ; Release: 8.6 ; Codename: jessie
• Epic Color: ghx-label-6
• Assignee: Sheng Wang
• Reporter: Sheng Wang
• Created: 26/Sep/19 07:34
• Updated: 13/Feb/20 22:21

Description

I created kudu managerd table as below:

create table if not exists kudu_test_table(
  logDay string,
  id int,
  primary key(logDay,id))
PARTITION BY RANGE (logDay)
(PARTITION VALUE = '2019-09-20')
STORED AS KUDU TBLPROPERTIES ('kudu.master_addresses'='master1:7051,master2:7051,master3:7051');

The query return failed. We connected to mysql directly instead of use HMS. I've already read the related code, and I'd like to try to solve this problem.

 

 

Issue Links

• is related to: IMPALA-9266 TestLogFragments.test_log_fragments fails due to missing log
• is related to: IMPALA-9264 Support catalogd without HMS
• is related to: IMPALA-9287 test_kudu_table_create_without_hms fails on Hive-3 environment