[
https://issues.apache.org/jira/browse/IMPALA-8974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16947322#comment-16947322
]
WangSheng commented on IMPALA-8974:
-----------------------------------
Here is the gerrit URL: http://gerrit.cloudera.org:8080/14398
> Create kudu table failed when catalogd connected to mysql directly instead of
> use HMS
> -------------------------------------------------------------------------------------
>
> Key: IMPALA-8974
> URL: https://issues.apache.org/jira/browse/IMPALA-8974
> Project: IMPALA
> Issue Type: Bug
> Components: Frontend
> Affects Versions: Impala 3.3.0
> Environment: Distributor ID: Debian
> Description: Debian GNU/Linux 8.6 (jessie)
> Release: 8.6
> Codename: jessie
> Reporter: WangSheng
> Assignee: WangSheng
> Priority: Major
> Attachments: error.png
>
>
> I created kudu managerd table as below:
>
> {code:java}
> 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');
> {code}
> The table in impala created successful, but in kudu storage 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.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
