[
https://issues.apache.org/jira/browse/IMPALA-13893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yida Wu resolved IMPALA-13893.
------------------------------
Fix Version/s: Impala 5.0.0
Resolution: Fixed
> Tuple caching correctness verification fails for
> query_test.test_queries.TestQueriesTextTables.test_random
> ----------------------------------------------------------------------------------------------------------
>
> Key: IMPALA-13893
> URL: https://issues.apache.org/jira/browse/IMPALA-13893
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 5.0.0
> Reporter: Joe McDonnell
> Assignee: Yida Wu
> Priority: Major
> Fix For: Impala 5.0.0
>
>
> When running with tuple cache correctness verification,
> query_test.test_queries.TestQueriesTextTables.test_random fails with the
> following error:
> {noformat}
> query_test/test_queries.py:256: in test_random
> self.run_test_case('QueryTest/random', vector)
> common/impala_test_suite.py:874: in run_test_case
> result = exec_fn(query, user=test_section.get('USER', '').strip() or None)
> common/impala_test_suite.py:804: in __exec_in_impala
> result = self.__execute_query(target_impalad_client, query, user=user)
> common/impala_test_suite.py:1286: in __execute_query
> return impalad_client.execute(query, user=user)
> common/impala_connection.py:462: in execute
> fetch_profile_after_close=fetch_profile_after_close)
> beeswax/impala_beeswax.py:193: in execute
> handle = self.__execute_query(query_string.strip(), user=user)
> beeswax/impala_beeswax.py:289: in __execute_query
> self.wait_for_finished(handle)
> beeswax/impala_beeswax.py:315: in wait_for_finished
> raise ImpalaBeeswaxException(error_log, None)
> E ImpalaBeeswaxException: Query 534df8c1bbfdca0e:57bc605100000000 failed:
> E Inconsistent tuple cache found: Failed to open file
> '/data/jenkins/workspace/tmp/impala-tuplecache-debugdump-0/tuple-cache-debug-dump/c5ee5de51167923509373f3adfd81a17_1709992867/534df8c1bbfdca0e:57bc605100000000_bb4715c6f083597c:0cbf03f200000000_ref.bad'.{noformat}
> What's happening is that two tuple caching locations have the same cache key
> because they are scanning the same table. Tuple caching correctness
> verification fails because one location has already removed locations when
> the other wants to do correctness verification. One way to fix this is to
> incorporate the plan node id into the filenames.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
