You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "David Mollitor (Jira)" <ji...@apache.org> on 2021/05/20 20:12:00 UTC
[jira] [Commented] (IMPALA-10710) Log When Kudu Table Already
Exists in HMS
[ https://issues.apache.org/jira/browse/IMPALA-10710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17348781#comment-17348781 ]
David Mollitor commented on IMPALA-10710:
-----------------------------------------
OK, so first off, I was looking at an older version of Impala (pre: IMPALA-8984) so it looks like this was already tackled once. I would though like to simplify and to add additional logging.
> Log When Kudu Table Already Exists in HMS
> -----------------------------------------
>
> Key: IMPALA-10710
> URL: https://issues.apache.org/jira/browse/IMPALA-10710
> Project: IMPALA
> Issue Type: Improvement
> Reporter: David Mollitor
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> As I understand the code, Impala performs HMS/Kudu {{CREATE TABLE}} interaction as:
> * Create the table in Kudu
> * Register table with HMS
> * Drop the Kudu table on HMS error
> This is generally OK, except that it drops the table from Kudu on a {{TableAlreadyExists}} Exception.
> So, if I issue the same {{CREATE TABLE}} statement twice, the data will be dropped from Kudu on the second execution.
> This applies only to {{IF NOT EXISTS}} statements.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org