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

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IMPALA-9017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16947267#comment-16947267 ] 

ASF subversion and git services commented on IMPALA-9017:
---------------------------------------------------------

Commit 4f8a1b9b088e44821c59710c353a13c94f85d305 in impala's branch refs/heads/master from Anurag Mantripragada
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=4f8a1b9 ]

IMPALA-9017: Alter table events on dropped table/db should be
ignored.

Alter table events received on a table/db that does not exist in
catalog can be safely ignored. This is because a table not present
in the catalog means either:
  1. The table was created in HMS but not processed by the events
     processor beacuase it is already in an error state or,
  2. It was dropped/renamed by the same catalog.

Prior to this change, alter table events generated by renames would
try to add the new table names to the cache irrespective of weather
old table was in catalog cache. After this change a drop + create
sequence happens only if table before rename exists in catalog.

Testing:
Added tests for rename + drop table/db sequences to verify events
processor does not error out.

Change-Id: I534accd704f76772ebe47865eff0fcdc7a033a48
Reviewed-on: http://gerrit.cloudera.org:8080/14385
Reviewed-by: Vihang Karajgaonkar <vi...@cloudera.com>
Tested-by: Impala Public Jenkins <im...@cloudera.com>


> 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
>            Priority: Major
>
> 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)

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