IMPALA-4584: Make alter table operations on Kudu tables synchronous

This commit changes the behavior of alter table operations on Kudu
tables from asynchronous to synchronous. With this change, alter table
operations return when either the operations complete successfully or
a timeout is reached.

Change-Id: I385bce66691ae9040e72f97557e1bba31009e36b
Reviewed-on: http://gerrit.cloudera.org:8080/5364
Reviewed-by: Dimitris Tsirogiannis <dtsirogiannis@cloudera.com>
Tested-by: Internal Jenkins
This commit is contained in:
Dimitris Tsirogiannis
2016-12-05 13:14:50 -08:00
committed by Internal Jenkins
parent 9f387c8583
commit 5bb9959fa4
2 changed files with 36 additions and 28 deletions

View File

@@ -50,7 +50,6 @@ BIGINT
# Create a table with range distribution
create table tbl_to_alter (id int primary key, name string null, vali bigint not null)
distribute by range (id) (partition 1 < values <= 10) stored as kudu
tblproperties('kudu.table_name'='tbl_to_alter')
---- RESULTS
====
---- QUERY
@@ -296,7 +295,7 @@ alter table tbl_to_alter set tblproperties('kudu.table_name'='kudu_tbl_to_alter'
---- QUERY
# Create a new table and try to rename to an existing kudu table
create table copy_of_tbl (a int primary key) distribute by hash (a) into 3 buckets
stored as kudu;
stored as kudu tblproperties('kudu.table_name'='copy_of_tbl');
alter table copy_of_tbl set tblproperties('kudu.table_name'='kudu_tbl_to_alter')
---- CATCH
ImpalaRuntimeException: Error renaming Kudu table copy_of_tbl to kudu_tbl_to_alter