[
https://issues.apache.org/jira/browse/IMPALA-13285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17993039#comment-17993039
]
Quanlong Huang commented on IMPALA-13285:
-----------------------------------------
In Apache Hive 3.1.3, HMS doesn't provide the RPC to retrive the write events
info of a transaction. This RPC is added since Hive 4.0.0:
[https://github.com/apache/hive/blob/rel/release-4.0.0/standalone-metastore/metastore-common/src/main/thrift/hive_metastore.thrift#L3241]
Note that COMMIT_TXN event just contains a transaction id. I think we can't
implement the same logic as we did on CDP Hive 3:
https://github.com/apache/impala/blob/191aec5298e6f5e2ca352f19b9abb3b111232554/fe/src/compat-hive-3/java/org/apache/impala/compat/MetastoreShim.java#L901-L902
We can ignore these COMMIT_TXN events to avoid them break EventProcessor.
> Handle CommitTxnEvent on Hive3
> ------------------------------
>
> Key: IMPALA-13285
> URL: https://issues.apache.org/jira/browse/IMPALA-13285
> Project: IMPALA
> Issue Type: Bug
> Components: Catalog
> Reporter: Quanlong Huang
> Priority: Major
>
> As memtioned by [~eub] in IMPALA-10871, CommitTxnEvent is not correctly
> handled by Impala when building on Apache Hive3. This tracks the work of
> fixing the bug.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
