[IMPALA-12591] Consider using getTableIfCached() in Analyzer#dbContainsTable()

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Epic Color: ghx-label-7
• Assignee: Unassigned
• Reporter: Quanlong Huang
• Created: 04/Dec/23 07:01
• Updated: 04/Dec/23 07:02

Description

In the review of IMPALA-11501, fangyurao found REFRESH <table> would trigger metadata loading in local catalog mode:
https://gerrit.cloudera.org/c/20742/1/tests/authorization/test_ranger.py#1610

The cause is db.getTable() is called in Analyzer#dbContainsTable():
https://github.com/apache/impala/blob/4c762725c707f8d150fe250c03faf486008702d4/fe/src/main/java/org/apache/impala/analysis/Analyzer.java#L3847
In local catalog mode, coordinator will load the table metadata for db.getTable(). If callers just want to check existence of a table, they should use db.getTableIfCached() instead (added in IMPALA-8606).

This JIRA is to examine the usages of Analyzer#dbContainsTable() and see if we can use getTableIfCached() in it. Note that some comments point out that getTable() is unwanted:
https://github.com/apache/impala/blob/4c762725c707f8d150fe250c03faf486008702d4/fe/src/main/java/org/apache/impala/analysis/ResetMetadataStmt.java#L162C1-L165C91

Issue Links

• relates to: IMPALA-11501 Add flag to allow metadata-cache operations on masked tables