You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@impala.apache.org by "rongchuan.jin (Jira)" <ji...@apache.org> on 2022/12/26 08:00:00 UTC

[jira] [Created] (IMPALA-11813) Handling AlterTableEvent operation in Automatic Invalidate/Refresh of metadata should be invalidate rather than reload

rongchuan.jin created IMPALA-11813:
--------------------------------------

             Summary: Handling AlterTableEvent operation in Automatic Invalidate/Refresh of metadata should be invalidate rather than reload
                 Key: IMPALA-11813
                 URL: https://issues.apache.org/jira/browse/IMPALA-11813
             Project: IMPALA
          Issue Type: Bug
          Components: Catalog
    Affects Versions: Impala 4.1.1, Impala 4.2.0, Impala 4.1.0
            Reporter: rongchuan.jin


As the [docs|https://impala.apache.org/docs/build/html/topics/impala_metadata.html] said, metastoreEventProcessor invalidates the tables when it receives the ALTER TABLE event.
But in fact, we still use reloadTable to handle alterTableEvent, see in [code|https://github.com/apache/impala/blob/branch-4.2.0/fe/src/main/java/org/apache/impala/catalog/events/MetastoreEvents.java#L1448]，which is inconsistent and may leads to unexpected metastore sync thread shutdown. 



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