[
https://issues.apache.org/jira/browse/IMPALA-14468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltán Borók-Nagy resolved IMPALA-14468.
----------------------------------------
Fix Version/s: Impala 5.0.0
Resolution: Fixed
> Workload management throws TableNotFoundException: Table not found:
> sys.impala_query_log on first execution
> -----------------------------------------------------------------------------------------------------------
>
> Key: IMPALA-14468
> URL: https://issues.apache.org/jira/browse/IMPALA-14468
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Reporter: Zoltán Borók-Nagy
> Assignee: Zoltán Borók-Nagy
> Priority: Major
> Labels: workload-management
> Fix For: Impala 5.0.0
>
>
> When Workload management is used first, CatalogD reports error Table not
> found: sys.impala_query_log. (also for sys.impala_query_live)
> It is because during InitWorkloadManagement() we issue a ResetMetadata()
> request against sys.impala_query_log to retrieve its schema version. If the
> request fails with TableNotFound, we create the table. In other words, the
> current initialization of workload management generates error messages even
> when everything is going fine, and this can confuse users.
> Instead of calling ResetMetadata() we can test the existence of the workload
> management tables (sys.impala_query_log and sys.impala_query_live) first.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
