[
https://issues.apache.org/jira/browse/IMPALA-13519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Fehr updated IMPALA-13519:
--------------------------------
Epic Link: IMPALA-12427
> 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
> Priority: Major
> Labels: calcite, frontend
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
