Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
1.0.1
-
None
Description
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.