You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Jason Fehr (Jira)" <ji...@apache.org> on 2024/11/06 19:12:00 UTC
[jira] [Created] (IMPALA-13519) Calcite Planner Does Not Set Workload Management Data
Jason Fehr created IMPALA-13519:
-----------------------------------
Summary: Calcite Planner Does Not Set Workload Management Data
Key: IMPALA-13519
URL: https://issues.apache.org/jira/browse/IMPALA-13519
Project: IMPALA
Issue Type: Bug
Components: Frontend
Reporter: Jason Fehr
Assignee: Steve Carlin
Workload management writes the tables queried and the select, join, where, aggregate, order by columns to the sys.impala_query_log table. This data is determined by the frontend planner and returned to the backend coordinator via the [TExecRequest object|https://github.com/apache/impala/blob/88e0e4e8baa97f7fded12230b14232dc85cf6d79/common/thrift/Frontend.thrift#L702-L718].
The Calcite planner needs to provide this information as well on the TExecRequest object is creates.
The [test_workload_mgmt_sql_details.py|https://github.com/apache/impala/blob/master/tests/custom_cluster/test_workload_mgmt_sql_details.py] custom cluster test is the best test to determine if Calcite is generating the correct values for each piece of data.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org