[
https://issues.apache.org/jira/browse/IMPALA-14468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18023438#comment-18023438
]
ASF subversion and git services commented on IMPALA-14468:
----------------------------------------------------------
Commit 4e2a81161a0093a3abc330cf7c845567e29d742a in impala's branch
refs/heads/master from Zoltan Borok-Nagy
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=4e2a81161 ]
IMPALA-14468: Don't generate errors during InitWorkloadManagement() when
everything goes fine
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 <[email protected]>
Reviewed-by: Riza Suminto <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> 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
>
> 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]
