You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Quanlong Huang (Jira)" <ji...@apache.org> on 2023/12/04 07:02:00 UTC

[jira] [Created] (IMPALA-12591) Consider using getTableIfCached() in

Quanlong Huang created IMPALA-12591:
---------------------------------------

             Summary: Consider using getTableIfCached() in 
                 Key: IMPALA-12591
                 URL: https://issues.apache.org/jira/browse/IMPALA-12591
             Project: IMPALA
          Issue Type: Bug
            Reporter: Quanlong Huang


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



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org