[ 
https://issues.apache.org/jira/browse/IMPALA-14233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18013331#comment-18013331
 ] 

ASF subversion and git services commented on IMPALA-14233:
----------------------------------------------------------

Commit e7676223df4861992e10cfcea727002fcfca73e9 in impala's branch 
refs/heads/master from Eyizoha
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=e7676223d ]

IMPALA-14233: Fix unexpected Kudu table drop attempt on external table creation 
failure

The existing code incorrectly attempts to drop the corresponding
Kudu table when the creation of a Kudu external table in HMS fails due
to an erroneous negation in the if condition (fortunately, there are
additional checks with Preconditions in KuduCatalogOpExecutor.dropTable,
causing such attempts to always fail). Additionally, when creating a
Kudu synchronized table, if the table creation fails in HMS, it will
unexpectedly skip deleting the corresponding Kudu table, resulting in an
"already exists in Kudu" error when retrying the table creation.

Removed the incorrect negation in the if condition to align with the
intended behavior described in the comment.

Testing:
 - Existing tests cover this change.

Change-Id: I67d1cb333526fa41f247757997a6f7cf60d26c0b
Reviewed-on: http://gerrit.cloudera.org:8080/23181
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> Creating Kudu external table failure leads to the corresponding Kudu table 
> being dropped
> ----------------------------------------------------------------------------------------
>
>                 Key: IMPALA-14233
>                 URL: https://issues.apache.org/jira/browse/IMPALA-14233
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Catalog
>    Affects Versions: Impala 4.5.0
>            Reporter: Zihao Ye
>            Assignee: Zihao Ye
>            Priority: Blocker
>
> There is a critical bug where, upon failing to create a Kudu external table, 
> it leads to the corresponding Kudu table being dropped.
> *Steps to Reproduce:*
>  # Attempt to create a Kudu external table with corresponding Kudu table.
>  # Ensure that the creation of the table failed (e.g., due to permission 
> denied).
>  # Observe that the corresponding Kudu table is deleted.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to