Files
impala/testdata/workloads/functional-query/queries/QueryTest/acid-insert.test
Zoltan Borok-Nagy 3e9cac0cac IMPALA-8854: fix acid insert tests
test_acid_nonacid_insert has been failing lately. HMS became more
strict about checking the capabilities of its clients. Seems like
the Python client doesn't set any capabilities for itself therefore
HMS rejects its attempts of creating and dropping tables.

Now instead of using the RESET utility from the e2e test framework
(to drop and re-create tables), the test is using a unique database
and creates the tables through Impala. Different file formats are
exercised with the help of the DEFAULT_FILE_FORMAT query option.

Change-Id: I3a82338a7820d0ee748c961c8656fa3319c3929c
Reviewed-on: http://gerrit.cloudera.org:8080/14064
Reviewed-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>
Tested-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>
2019-08-15 13:02:55 +00:00

131 lines
2.3 KiB
Plaintext

====
---- QUERY
create table insertonly_nopart (i int)
tblproperties('transactional'='true', 'transactional_properties'='insert_only');
insert into insertonly_nopart values (1), (2);
====
---- QUERY
select i from insertonly_nopart order by i;
---- RESULTS
1
2
---- TYPES
INT
====
---- QUERY
insert into insertonly_nopart values (3);
====
---- QUERY
select i from insertonly_nopart order by i;
---- RESULTS
1
2
3
---- TYPES
INT
====
---- QUERY
insert overwrite insertonly_nopart values (10);
====
---- QUERY
select i from insertonly_nopart order by i;
---- RESULTS
10
---- TYPES
INT
====
---- QUERY
insert overwrite insertonly_nopart select 100;
====
---- QUERY
select i from insertonly_nopart order by i;
---- RESULTS
100
---- TYPES
INT
====
---- QUERY
insert overwrite insertonly_nopart
select * from insertonly_nopart limit 0;
====
---- QUERY
select i from insertonly_nopart order by i;
---- RESULTS
---- TYPES
INT
====
---- QUERY
create table if not exists insertonly_part (i int)
partitioned by (p int)
tblproperties('transactional'='true', 'transactional_properties'='insert_only');
insert into insertonly_part partition (p=1) values (10), (11);
insert into insertonly_part partition (p=2) values (20);
====
---- QUERY
select p, i from insertonly_part order by i;
---- RESULTS
1,10
1,11
2,20
---- TYPES
INT,INT
====
---- QUERY
insert into insertonly_part partition (p=2) values (21);
insert into insertonly_part partition (p=3) values (30);
====
---- QUERY
select p, i from insertonly_part order by i;
---- RESULTS
1,10
1,11
2,20
2,21
3,30
---- TYPES
INT,INT
====
---- QUERY
insert overwrite insertonly_part partition (p=2) values (22);
insert overwrite insertonly_part partition (p=3) values (31);
====
---- QUERY
select p, i from insertonly_part order by i;
---- RESULTS
1,10
1,11
2,22
3,31
---- TYPES
INT,INT
====
---- QUERY
insert overwrite insertonly_part partition (p=1)
select * from insertonly_nopart limit 0;
insert overwrite insertonly_part partition (p=2)
select * from insertonly_nopart limit 0;
====
---- QUERY
select p, i from insertonly_part order by i;
---- RESULTS
3,31
---- TYPES
INT,INT
====
---- QUERY
insert overwrite insertonly_part partition (p)
values (1000, 1), (2000, 2), (4000, 4), (5000, 5), (5001, 5);
====
---- QUERY
select p, i from insertonly_part order by p, i;
---- RESULTS
1,1000
2,2000
3,31
4,4000
5,5000
5,5001
---- TYPES
INT,INT
====