[IMPALA-10092] Some tests in custom_cluster/test_kudu.py do not run even they are not explicitly disabled.

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: Impala 4.0.0
• Component/s: Infrastructure
• Labels: kudu test
• Epic Color: ghx-label-6
• Assignee: Fang-Yu Rao
• Reporter: Fang-Yu Rao
• Created: 18/Aug/20 22:05
• Updated: 23/Oct/20 16:41
• Resolved: 23/Oct/20 16:41

Description

We found that the following tests in https://github.com/apache/impala/blob/master/tests/custom_cluster/test_kudu.py do not run even we remove all the decorators like "@SkipIfKudu.no_hybrid_clock" or "@SkipIfHive3.kudu_hms_notifications_not_supported" to skip the tests.

1. TestKuduOperations::test_local_tz_conversion_ops
2. TestKuduClientTimeout::test_impalad_timeout
3. TestKuduHMSIntegration::test_create_managed_kudu_tables
4. TestKuduHMSIntegration::test_kudu_alter_table

This may be due to the fact that we add at https://github.com/apache/impala/blob/master/tests/common/custom_cluster_test_suite.py#L78-L80 a constraint that only allows 'table_format' to be "text/none", i.e., 'file_format' has to be "text" and 'compression_codec' has to be "none". It can be verified that by removing this constraint, the tests above could be run after removing all the decorators with 'table_format' being "kudu/none", which is added according to https://github.com/apache/impala/blob/master/tests/common/test_dimensions.py#L116-L119.

In this regard, we may need to override the class method of add_test_dimensions() of the classes of TestKuduOperations, TestKuduClientTimeout, and TestKuduHMSIntegration so that once those currently disabled Kudu tests are re-enabled, those tests involving the test vector could be run.

Issue Links

• is related to: IMPALA-9990 Kudu table ownership