Joe McDonnell created IMPALA-11903:
--------------------------------------

             Summary: Ozone tests failing due to mismatch in ERASURECODE_POLICY
                 Key: IMPALA-11903
                 URL: https://issues.apache.org/jira/browse/IMPALA-11903
             Project: IMPALA
          Issue Type: Bug
          Components: Infrastructure
    Affects Versions: Impala 4.3.0
            Reporter: Joe McDonnell


There are several test failures on Ozone test. All the diffs are based on the 
values for ERASURE_POLICY not matching (THREE vs NONE). Example:
{noformat}
metadata/test_compute_stats.py:64: in test_compute_stats_avro
    self.run_test_case('QueryTest/compute-stats-avro', vector, unique_database)
common/impala_test_suite.py:743: in run_test_case
    self.__verify_results_and_errors(vector, test_section, result, use_db)
common/impala_test_suite.py:579: in __verify_results_and_errors
    replace_filenames_with_placeholder)
common/test_result_verifier.py:469: in verify_raw_results
    VERIFIER_MAP[verifier](expected, actual)
common/test_result_verifier.py:278: in verify_query_result_is_equal
    assert expected_results == actual_results
E   assert Comparing QueryTestResults (expected vs actual):
E     '2009','1',310,1,regex:.*,'NOT CACHED','NOT 
CACHED','AVRO','false',regex:.*,'NONE' != '2009','1',310,1,'6.77KB','NOT 
CACHED','NOT 
CACHED','AVRO','false','ofs://localhost:9862/impala/test-warehouse/alltypes_avro_snap/year=2009/month=1','THREE'{noformat}
[https://github.com/apache/impala/blob/master/testdata/workloads/functional-query/queries/QueryTest/compute-stats-avro.test#L68-L97]

This applies across several a few dozen tests including:

authorization.test_ranger.TestRanger.test_grant_revoke_with_role

metadata.test_compute_stats.TestComputeStats.test_compute_stats_avro

metadata.test_ddl.TestDdlStatements.test_truncate_table

and several others.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to