mirror of
https://github.com/apache/impala.git
synced 2025-12-25 02:03:09 -05:00
IMPALA-8636: fix flakiness of ACID INSERT tests
I had to add @UniqueDatabase.parametrize(sync_ddl=True) to some e2e tests because they were broken in exhaustive mode. When the tests run with sync_ddl=True then the test files are executed against multiple impalads which means that each statement in the .test file is executed against a random impalad. Change-Id: Ic724e77833ed9ea58268e1857de0d33f9577af8b Reviewed-on: http://gerrit.cloudera.org:8080/13966 Reviewed-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com> Tested-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>
This commit is contained in:
committed by
Impala Public Jenkins
parent
e8bd307941
commit
48bb93d474
@@ -155,11 +155,13 @@ class TestInsertQueries(ImpalaTestSuite):
|
||||
self.hive_client.setMetaConf("metastore.client.capability.check", capability_check)
|
||||
|
||||
@SkipIfHive2.acid
|
||||
@UniqueDatabase.parametrize(sync_ddl=True)
|
||||
def test_acid_nonacid_insert(self, vector, unique_database):
|
||||
self.run_test_case('QueryTest/acid-nonacid-insert', vector, unique_database,
|
||||
multiple_impalad=vector.get_value('exec_option')['sync_ddl'] == 1)
|
||||
|
||||
@SkipIfHive2.acid
|
||||
@UniqueDatabase.parametrize(sync_ddl=True)
|
||||
def test_acid_insert_fail(self, vector, unique_database):
|
||||
self.run_test_case('QueryTest/acid-insert-fail', vector, unique_database,
|
||||
multiple_impalad=vector.get_value('exec_option')['sync_ddl'] == 1)
|
||||
|
||||
Reference in New Issue
Block a user