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

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

Commit 0b5a9889ee39a7df816efc6476aae2624f82f377 in impala's branch 
refs/heads/master from Vihang Karajgaonkar
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=0b5a988 ]

IMPALA-9946: Use table id when comparing transactional state

This change adds support for catalog clients to optionally
provide a table id when fetching the table metadata
using the GetPartialCatalogObject API. This table id
is used to compare the catalog table is same as the one
which is requested by client. If the table id matches, we compare the
ValidWriteIdList to provide a consistent view of the metadata to the
clients.

Testing:
Added a new test which drops and recreates the table from hive to
introduce the false positive in the existing ValidWriteIdList
comparison logic. After the patch, the test succeeds.

Change-Id: I58c5bd58c4eb5663647c01ecd738b661e4e4cd74
Reviewed-on: http://gerrit.cloudera.org:8080/16170
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> 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
>
> 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)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to