[IMPALA-9486] Creating a Kudu table via JDBC fails with "IllegalArgumentException"

• Type: Bug
• Status: Open
• Priority: Blocker
• Resolution: Unresolved
• Affects Version/s: Impala 3.2.0
• Component/s: Catalog
• Epic Color: ghx-label-14
• Assignee: Fang-Yu Rao
• Reporter: Grant Henke
• Created: 11/Mar/20 15:28
• Updated: 07/Sep/23 22:16

Description

A Kudu user reported that though creating tables via impala shell or Hue, when using an external tool connected via JDBC the create statement fails with the following:

[ImpalaJDBCDriver](500051) ERROR processing query/statement. Error Code: 0, SQL state: TStatus(statusCode:ERROR_STATUS, sqlState:HY000, errorMessage:ImpalaRuntimeException: Error creating Kudu table 'impala::default.foo' CAUSED BY: IllegalArgumentException: table owner must not be null or empty ), Query: …

 

When debugging the issue further it looks like the call to set the owner on the Kudu table should not be called if an owner is not explicitly set:

https://github.com/apache/impala/blob/497a17dbdc0669abd47c2360b8ca94de8b54d413/fe/src/main/java/org/apache/impala/service/KuduCatalogOpExecutor.java#L252

 

A possible fix could be to guard the call with isSetOwner:

if (msTbl.isSetOwner()) { 
   tableOpts.setOwner(msTbl.getOwner()); 
}

Issue Links

• relates to: IMPALA-10027 Use anonymous user when user is not specified