Created on 02-28-2020 10:06 AM - last edited on 02-28-2020 11:01 AM by cjervis
Hello,
We've recently migrated CDH from 5.16.2 to 6.3.3 and we now have the following message when we create a table using Impala JDBC driver (we are using the latest version 2.6.15.1017).
errorMessage:ImpalaRuntimeException: Error creating Kudu table 'impala::pdo.discoveries'
CAUSED BY: IllegalArgumentException: table owner must not be null or empty
When the same "create table" statement is executed in impala-shell, it works perfectly well.
The search for this error message in google did not find much result.
Any idea about the root cause ?
Created 03-02-2021 04:09 AM
Hello,
I got the same issue as yours. I am running Kudu and Impala in docker. I can create tables from impala-shell but not using JDBC driver.
Is there any solution for this?
Created 03-02-2021 04:09 AM
Hello,
I got the same issue as yours. I am running Kudu and Impala in docker. I can create tables from impala-shell but not using JDBC driver.
Is there any solution for this?
Created on 03-04-2021 05:16 AM - edited 03-04-2021 06:56 AM
Hello,
I tried with AuthMech=2 with UID as mentioned in the Cloudera Impala JDBC Driver documentation but I got HIveServer2 connection issue.
When I tried with AuthMech=0, along with UID (In my case no authentication is needed), it resolved the table owner error.
My connection string looks like -
jdbc:impala://localhost:21050/default;UseSasl=0;AuthMech=0;UID=impala
Hope this will resolve your issue as well.
Created 03-02-2021 09:15 PM
Hi @JeromeAlbin
Looks like https://issues.apache.org/jira/browse/IMPALA-9486
The Error pop up because you are connecting to Impala anonymously (no user, no password).
You can specify a user (even if it's not declared in Kudu), then it should work
Please read the page 12 of the following document: https://docs.cloudera.com/documentation/other/connectors/impala-jdbc/2-6-15/Cloudera-JDBC-Driver-for...
Using User Name
-----------------------
This authentication mechanism requires a user name but does not require a password.
The user name labels the session, facilitating database tracking.
Does that answer your question ? if yes, then feel free to mark this post "accept as solution"
Regards,
vipin