You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Vihang Karajgaonkar (Jira)" <ji...@apache.org> on 2020/07/10 19:38:00 UTC
[jira] [Resolved] (IMPALA-9913) Use table id to detect uniqueness
of table for drop table event
[ https://issues.apache.org/jira/browse/IMPALA-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vihang Karajgaonkar resolved IMPALA-9913.
-----------------------------------------
Fix Version/s: Impala 4.0
Resolution: Fixed
> Use table id to detect uniqueness of table for drop table event
> ---------------------------------------------------------------
>
> Key: IMPALA-9913
> URL: https://issues.apache.org/jira/browse/IMPALA-9913
> Project: IMPALA
> Issue Type: Improvement
> Reporter: Vihang Karajgaonkar
> Assignee: Vihang Karajgaonkar
> Priority: Minor
> Fix For: Impala 4.0
>
>
> When a DROP_TABLE event is received by the EventsProcessor, it needs to make a determination of whether the table in the cache is same as the table in the event. Without a unique id from the HMS it uses {{createTime}} field of the HMS table object to determine if the table matches with the table in the event.
> Since then HMS API was enhanced to include an {{id}} field which is guaranteed to unique accross all the tables (even the past deleted tables). Instead of the using createTime we should use id field to do the matching.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)