[
https://issues.apache.org/jira/browse/IMPALA-9486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17057294#comment-17057294
]
Grant Henke commented on IMPALA-9486:
-------------------------------------
It looks like a workaround for this is to specify a user when connecting.
However, in an unsecured environment that shouldn't be required.
> Creating a Kudu table via JDBC fails with "IllegalArgumentException"
> --------------------------------------------------------------------
>
> Key: IMPALA-9486
> URL: https://issues.apache.org/jira/browse/IMPALA-9486
> Project: IMPALA
> Issue Type: Bug
> Components: Catalog
> Affects Versions: Impala 3.2.0
> Reporter: Grant Henke
> Priority: Blocker
>
> 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:
> {noformat}
> [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: …
> {noformat}
>
> 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_:
> {code:java}
> if (msTbl.isSetOwner()) {
> tableOpts.setOwner(msTbl.getOwner());
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
