IMPALA-9022: Fixed test_query_profile_storage_load_time_filesystem
Skip part of the test which can be affected by the random behavor
of Catalog V2. The major purpose of the test is to verify storage
load time can be in query profile when metadata loading happens,
which is not affected by the change.
Change-Id: I6ee1afec6f2b706bc28b270aad731a138662490a
Reviewed-on: http://gerrit.cloudera.org:8080/14387
Reviewed-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>
Tested-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>
diff --git a/tests/query_test/test_observability.py b/tests/query_test/test_observability.py
index b1035ab..81840ca 100644
--- a/tests/query_test/test_observability.py
+++ b/tests/query_test/test_observability.py
@@ -710,8 +710,10 @@
storageLoadTime = "storage-load-time"
assert storageLoadTime in runtime_profile
# Call the second time, no metastore loading needed.
- runtime_profile = self.execute_query(query).runtime_profile
- assert storageLoadTime not in runtime_profile
+ # Only check this part in Catalog V1 because of V2's random behavior
+ if not cluster_properties.is_catalog_v2_cluster():
+ runtime_profile = self.execute_query(query).runtime_profile
+ assert storageLoadTime not in runtime_profile
def __verify_hashtable_stats_profile(self, runtime_profile):
assert "Hash Table" in runtime_profile
