mirror of
https://github.com/apache/impala.git
synced 2025-12-19 18:12:08 -05:00
4e2a81161a
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. Testing * tested manually that the error logs disappear Change-Id: Ic7f7c92bda57d9fdc2185bf4ef8fd4f09aea0879 Reviewed-on: http://gerrit.cloudera.org:8080/23470 Reviewed-by: Michael Smith <michael.smith@cloudera.com> Reviewed-by: Riza Suminto <riza.suminto@cloudera.com> Tested-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>