Impala Public Jenkins has submitted this change and it was merged. ( 
http://gerrit.cloudera.org:8080/16170 )

Change subject: IMPALA-9946: Use table id when comparing transactional state
......................................................................

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]>
---
M common/thrift/CatalogService.thrift
M fe/src/main/java/org/apache/impala/catalog/CatalogServiceCatalog.java
M fe/src/main/java/org/apache/impala/util/AcidUtils.java
M fe/src/test/java/org/apache/impala/catalog/PartialCatalogInfoWriteIdTest.java
M shaded-deps/pom.xml
5 files changed, 135 insertions(+), 8 deletions(-)

Approvals:
  Impala Public Jenkins: Looks good to me, approved; Verified

--
To view, visit http://gerrit.cloudera.org:8080/16170
To unsubscribe, visit http://gerrit.cloudera.org:8080/settings

Gerrit-Project: Impala-ASF
Gerrit-Branch: master
Gerrit-MessageType: merged
Gerrit-Change-Id: I58c5bd58c4eb5663647c01ecd738b661e4e4cd74
Gerrit-Change-Number: 16170
Gerrit-PatchSet: 6
Gerrit-Owner: Vihang Karajgaonkar <[email protected]>
Gerrit-Reviewer: Anurag Mantripragada <[email protected]>
Gerrit-Reviewer: Impala Public Jenkins <[email protected]>
Gerrit-Reviewer: Quanlong Huang <[email protected]>
Gerrit-Reviewer: Vihang Karajgaonkar <[email protected]>

Reply via email to