Skip to main content
thewayofthinkin
thewayofthinkin
Gold ⭐️
February 12, 2020
Solved

Failed to create table with kudu storage ( CDH 6.3 )

My current environment is CDH 6.3.2
  • Impala v3.2.0-cdh6.3.2
  • kudu 1.10.0-cdh6.3.2
Somehow, creating table with kudu storage gives IllegalArgumentException. It was ok with kudu 1.7.0-cdh5.16.2

CREATE TABLE test_mlee
(
id BIGINT,
name STRING,
PRIMARY KEY(id)
)
PARTITION BY HASH PARTITIONS 16
STORED AS KUDU
ERROR: IllegalArgumentException: null

 Any comment is appreciated Thank you in advance.

thewayofthinkin
thewayofthinkinAnswer
Gold ⭐️
February 13, 2020

@attilabukor 

Hi, Thank you for your comment.

Yesterday, I got a comment from HaoHao about this issue.

The issue not being able to create KUDU table on CDH 6.3.2 is related to remote HMS configuration in hive-site.xml

 

KuduTable.java ( on CDH 6.3.2 ) has a logic validating if `hmsuris` is null or empty.

If `hmsuris` is empty or null, it raises exception and fails.

 

This has been fixed on master branch, but I'm not sure if this fix will be delivered with CDH 6.3.3

Can you confirm if the fix is shipped with CDH 6.3.3?

 

Here is the bug report ticket.

 

View in thread

2 replies

attilabukor
Gold ⭐️
attilabukor
Gold ⭐️
February 13, 2020

Hi, it seems you didn't specify what column to partition by. Maybe in previous version Impala was able to infer it in case, but I don't think this was ever an intended behavior, maybe a fortunate side effect of a bug that was fixed since. In any case, you need to write

PARTITION BY HASH(id)

 

Translate
thewayofthinkin
thewayofthinkinAuthorAnswer
Gold ⭐️
February 13, 2020

@attilabukor 

Hi, Thank you for your comment.

Yesterday, I got a comment from HaoHao about this issue.

The issue not being able to create KUDU table on CDH 6.3.2 is related to remote HMS configuration in hive-site.xml

 

KuduTable.java ( on CDH 6.3.2 ) has a logic validating if `hmsuris` is null or empty.

If `hmsuris` is empty or null, it raises exception and fails.

 

This has been fixed on master branch, but I'm not sure if this fix will be delivered with CDH 6.3.3

Can you confirm if the fix is shipped with CDH 6.3.3?

 

Here is the bug report ticket.

 

Translate
Terms & ConditionsAccessibility statement