[
https://issues.apache.org/jira/browse/IMPALA-14219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18004886#comment-18004886
]
Joe McDonnell commented on IMPALA-14219:
----------------------------------------
This impacts test_fuzz_parquet_v2 and test_fuzz_nested_types.
> test_scanners_fuzz.py runs some queries against the wrong database with
> uncorrupted tables
> ------------------------------------------------------------------------------------------
>
> Key: IMPALA-14219
> URL: https://issues.apache.org/jira/browse/IMPALA-14219
> Project: IMPALA
> Issue Type: Task
> Components: Test
> Affects Versions: Impala 5.0.0
> Reporter: Joe McDonnell
> Priority: Major
>
> When working on IMPALA-13898, I discovered that
> "ImpalaTestSuite::_get_table_location()" actually switches into a database
> based on the vector (i.e. parquet switches into functional_parquet). When I
> changed this behavior to not switch databases, this broke some tests in
> test_scanners_fuzz.py. It turns out the tests were not running against the
> corrupted version of the tables. When they do run against the corrupted
> version of the table, Impala frequently crashes.
> Basically, the test creates a corrupted table in a unique_database based on
> an original base table and then runs SQLs against it. Some of the SQLs use
> relative names for the corrupted table (e.g. complextypestbl or
> alltypesagg_parquet_v2_uncompressed), which is the same as the base table.
> "ImpalaTestSuite::_get_table_location()" was switching them into
> functional_parquet which has tables of those names, and then nothing else
> ever switched them to the unique_database with the corrupted versions of the
> tables.
> We need to fix this test behavior, but we need to fix the Impala crashes
> before we can make these tests do the right thing.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
