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

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

Commit dc46aa48d9449729f312aaaa3312e0d8df150063 in impala's branch 
refs/heads/master from stiga-huang
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=dc46aa48d ]

IMPALA-13285: Ignore COMMIT_TXN events on Apache Hive 3

In Apache Hive 3, HMS doesn't provide the API to retrive WriteEvents
info of a given transaction. COMMIT_TXN event just contains a
transaction id so Impala can't process it.

This patch ignores COMMIT_TXN events when building on Apache Hive 3.
Some tests in MetastoreEventsProcessorTest and EventExecutorServiceTest
are skipped due to this.

Tests:
 - Manually tested on Apache Hive 3. Verified that EventProcessor still
   works after receiving COMMIT_TXN events.
 - Passed some tests in MetastoreEventsProcessorTest and
   EventExecutorServiceTest that previously failed due to EventProcessor
   going into ERROR state.

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


> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to