[
https://issues.apache.org/jira/browse/IMPALA-13603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17905588#comment-17905588
]
Jason Fehr commented on IMPALA-13603:
-------------------------------------
The test failure was not related to https://gerrit.cloudera.org/c/22200/.
Impala assigns a statement type of "UNKNOWN" to queries that fail due to a SQL
issue even if the syntax is correct. For example, the sql statement "describe
table_that_does_not_exist" is syntactically correct, but Impala will record
this query as having a type of "UNKNOWN".
Workload management skips recording [trivial
DDLs|https://github.com/apache/impala/blob/cb35dc87690b21a74acc7af599abd492db8cb52f/be/src/service/workload-management-worker.cc#L531-L546],
but only when those DDLs succeed because failed DDLs do not have the type
"DDL" but rather have the type "UNKNOWN". Hence, workload management cannot
determine if the failed query is a DDL that should not be logged versus a DML,
DDL, or Select query that should be logged.
This test failure occurred because the
[test_query_live.py|https://github.com/apache/impala/blob/cb35dc87690b21a74acc7af599abd492db8cb52f/tests/custom_cluster/test_query_live.py#L38]
tests all wait for the sys.impala_query_live table to appear by running the
DDL "describe sys.impala_query_live", and, in this one test run, that DDL
failed the first time it ran and thus workload management did not skip
recording it. The test asserts on an expected number of queries to be
available in the sys.impala_query_live table, and this one failed DDL increased
the actual count to be one greater than the expected count.
> 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]
