[
https://issues.apache.org/jira/browse/IMPALA-10710?focusedWorklogId=599934&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-599934
]
ASF GitHub Bot logged work on IMPALA-10710:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 20/May/21 17:32
Start Date: 20/May/21 17:32
Worklog Time Spent: 10m
Work Description: bartash commented on pull request #26:
URL: https://github.com/apache/impala/pull/26#issuecomment-845317868
Thank you for your interest in contributing to Impala! We do code review via
gerrit rather than GitHub PRs; you can see the process described at
https://cwiki.apache.org/confluence/display/IMPALA/Contributing+to+Impala
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 599934)
Time Spent: 20m (was: 10m)
> Do Not Drop Kudu Table When Table Already Exists in HMS
> -------------------------------------------------------
>
> Key: IMPALA-10710
> URL: https://issues.apache.org/jira/browse/IMPALA-10710
> Project: IMPALA
> Issue Type: Bug
> Reporter: David Mollitor
> Priority: Major
> Time Spent: 20m
> 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 message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
