You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Grant Henke (Jira)" <ji...@apache.org> on 2020/06/02 13:04:00 UTC

[jira] [Updated] (KUDU-1710) Handle IF [NOT] EXISTS during create and drop table through the Kudu API

     [ https://issues.apache.org/jira/browse/KUDU-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Grant Henke updated KUDU-1710:
------------------------------
    Labels: roadmap-candidate  (was: )

> Handle IF [NOT] EXISTS during create and drop table through the Kudu API
> ------------------------------------------------------------------------
>
>                 Key: KUDU-1710
>                 URL: https://issues.apache.org/jira/browse/KUDU-1710
>             Project: Kudu
>          Issue Type: Bug
>          Components: impala
>    Affects Versions: 1.0.1
>            Reporter: Dimitris Tsirogiannis
>            Priority: Major
>              Labels: roadmap-candidate
>
> Currently Impala handles IF [NOT] EXISTS for creating and dropping Kudu tables by first checking if the table exists and then making the associated API call to Kudu. However, these two operations are not atomic and hence may result in inconsistent states and weird error messages. Ideally, the Kudu API should handle the IF [NOT] EXISTS case and ensure atomicity. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)