[
https://issues.apache.org/jira/browse/IMPALA-13603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17906283#comment-17906283
]
ASF subversion and git services commented on IMPALA-13603:
----------------------------------------------------------
Commit 086e0b0ffa4abf284b52a3267e078f357e47de0a in impala's branch
refs/heads/master from jasonmfehr
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=086e0b0ff ]
IMPALA-13603: Fix Flaky Live Queries Table Tests
Workload management skips recording successful trivial DDLs but does
not skip recording failed trivial DDLs. The test_query_live.py tests
run a describe DDL in the setup_method(). Normally, this describe
succeeds immediately and thus is not recorded in the workload
management tables. However, in very rare instances, the describe DDL
will fail the first time and succeed the second time. These cases
result in an extra query recorded in the sys.impala_query_live table
and test assertions that rely on a certain number of records being in
this table fail because there are extra records.
This change modifies the method used to determine if the
sys.impala_query_live table is available. The test_query_live.py
tests now check the coordinator's catalog cache and wait until the
sys.impala_query_live table appears. DDLs are no longer executed.
All tests in the test_query_live.py file passed locally and in
Jenkins builds.
Change-Id: I767a2bd7b068ab3fdeddb7cb3c4b307844d2d279
Reviewed-on: http://gerrit.cloudera.org:8080/22210
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> TestQueryLive.test_query_live fails with AnalysisException: Could not resolve
> path: 'sys.impala_query_live'
> -----------------------------------------------------------------------------------------------------------
>
> Key: IMPALA-13603
> URL: https://issues.apache.org/jira/browse/IMPALA-13603
> Project: IMPALA
> Issue Type: Task
> Reporter: Pranav Yogi Lodha
> Assignee: Jason Fehr
> Priority: Major
> Labels: broken-build
>
> h2. Error Message
> {noformat}
> assert 4 == 3 + where 4 =
> len(['f64e438aa3c933a9:abc9b44e00000000\ttest_query_live',
> '9140fa71282388dc:b62ddbc300000000\ttest_query_live',
> 'fc489742ad1a015e:ef91e39700000000\ttest_query_live',
> 'e548334c1e811764:6fb49e3600000000\ttest_query_live']) + where
> ['f64e438aa3c933a9:abc9b44e00000000\ttest_query_live',
> '9140fa71282388dc:b62ddbc300000000\ttest_query_live',
> 'fc489742ad1a015e:ef91e39700000000\ttest_query_live',
> 'e548334c1e811764:6fb49e3600000000\ttest_query_live'] =
> <tests.beeswax.impala_beeswax.ImpalaBeeswaxResult object at
> 0x7fb3ca2fb210>.data{noformat}
> h2. Stacktrace
> {noformat}
> custom_cluster/test_query_live.py:95: in test_query_live assert
> len(result2.data) == 3 E assert 4 == 3 E + where 4 =
> len(['f64e438aa3c933a9:abc9b44e00000000\ttest_query_live',
> '9140fa71282388dc:b62ddbc300000000\ttest_query_live',
> 'fc489742ad1a015e:ef91e39700000000\ttest_query_live',
> 'e548334c1e811764:6fb49e3600000000\ttest_query_live']) E + where
> ['f64e438aa3c933a9:abc9b44e00000000\ttest_query_live',
> '9140fa71282388dc:b62ddbc300000000\ttest_query_live',
> 'fc489742ad1a015e:ef91e39700000000\ttest_query_live',
> 'e548334c1e811764:6fb49e3600000000\ttest_query_live'] =
> <tests.beeswax.impala_beeswax.ImpalaBeeswaxResult object at
> 0x7fb3ca2fb210>.data{noformat}
> h2. Standard Output
> {noformat}
> Query f64e438aa3c933a9:abc9b44e00000000 failed: AnalysisException: Could not
> resolve path: 'sys.impala_query_live'{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
