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/15 18:03:00 UTC

[jira] [Resolved] (IMPALA-9946) Use table id when comparing the the transactional state of the table

     [ https://issues.apache.org/jira/browse/IMPALA-9946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vihang Karajgaonkar resolved IMPALA-9946.
-----------------------------------------
    Fix Version/s: Impala 4.0
       Resolution: Fixed

> Use table id when comparing the the transactional state of the table
> --------------------------------------------------------------------
>
>                 Key: IMPALA-9946
>                 URL: https://issues.apache.org/jira/browse/IMPALA-9946
>             Project: IMPALA
>          Issue Type: Improvement
>            Reporter: Vihang Karajgaonkar
>            Assignee: Vihang Karajgaonkar
>            Priority: Major
>             Fix For: Impala 4.0
>
>
> IMPALA-9791 added support in catalog to return the table metadata which consistent with respect to a given {{ValidWriteIdList}}. In theory it is possible that this can give false positive (table is consistent with respect to the provided ValidWriteList but in reality its not). This can happen when the table is dropped and recreated with same name without the knowledge of catalog. We should compare the ValidWriteIdList only when the cached table's id matches with the tableId as provided by the client or from HMS.



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