You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Quanlong Huang (Jira)" <ji...@apache.org> on 2020/01/13 09:06:00 UTC
[jira] [Resolved] (IMPALA-8984) Submit several same kudu table
created query concurrently may result in table deleted in Kudu storage
[ https://issues.apache.org/jira/browse/IMPALA-8984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Quanlong Huang resolved IMPALA-8984.
------------------------------------
Fix Version/s: Impala 3.4.0
Resolution: Fixed
> Submit several same kudu table created query concurrently may result in table deleted in Kudu storage
> ------------------------------------------------------------------------------------------------------
>
> Key: IMPALA-8984
> URL: https://issues.apache.org/jira/browse/IMPALA-8984
> Project: IMPALA
> Issue Type: Bug
> Components: Frontend
> Affects Versions: Impala 3.3.0
> Reporter: WangSheng
> Assignee: WangSheng
> Priority: Critical
> Fix For: Impala 3.4.0
>
>
> If the below query submitted several times concurrently, the result could be: All these queries finished, and table created in HMS, but not exists in kudu storage. I've already found the reason, and I will submit the patch later.
> {code:java}
> create table if not exists test_kudu_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}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)