You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Anurag Mantripragada (Jira)" <ji...@apache.org> on 2019/10/07 20:31:00 UTC

[jira] [Created] (IMPALA-9017) Alter table events should be skipped if the table/db is not found in the catalog.

Anurag Mantripragada created IMPALA-9017:
--------------------------------------------

             Summary: Alter table events should be skipped if the table/db is not found in the catalog.
                 Key: IMPALA-9017
                 URL: https://issues.apache.org/jira/browse/IMPALA-9017
             Project: IMPALA
          Issue Type: Bug
          Components: Frontend
            Reporter: Anurag Mantripragada
            Assignee: Anurag Mantripragada


Currently, a sequence of alter_table, drop_table/db puts the events processor in an error state since the table/database are already dropped. However, it is safe to skip such events because the catalog is not aware of such tables because of either of the reasons:
 # The table creation event is missed by the catalog - this means the events processor is already in error state.
 # The table was later dropped/renamed.

In either case, it doesn't make sense to try to add the table to catalog.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)