cmunkey commented on PR #3365:
URL: https://github.com/apache/hive/pull/3365#issuecomment-1163905485
Changed the following since the last upload:
- Eliminated HMS client changes. The HMS client changes were used to query
HMS to get the databases updated for a AbortTxnEvent, in the case where the
event was used to notify the non transactional listeners. Currently only the
DbTxnListener which is a transactional listener needs the databases updated.
- Added unit test to make sure that old versions of the AbortTxnEvent can
still be serialiazed for the case where REPL DUMP may be processing events
logged by an older version.
- Modified TestReplicationFilters to do extra transactions on the replica
database to test out the source to target
transaction mapping. Currently this test is causing the following problems
that I am still debugging:
testTxnEventsOptimized() - to assert that transaction mapping was being
done correctly, I tried to check the REPL_TXN_MAP on the replica. But this
proved difficult because of the following:
o REPL_TXN_MAP is cleared during commit/abort, so it could not be
checked at the end of the test. Instead, I tried to capture the table in the
openTxn test listener. But it seemed like the extra SELECT that the test is
doing is causing some kind of deadlock in the code. Some of the sampling did
work, and I could see in the debugger the mapping, after a few times sampling,
the test gets a "org.apache.hadoop.hive.ql.lockmgr.LockException: Error
communicating with the metastore" exception.
o For the test to pass, I commented out the sampling of the REPL_TXN_MAP
table.
testTxnEventsUnoptimized() - this these was modified to burn some
transactions on the replica also. But when these extra transactions are burned,
on the replica, there is now extra openTxn() calls that are unexpected. This
test has the transaction filtering as OFF, so it should be default behavior, so
I am not sure what is going on. For the test to pass, I commented out the code
to burn the transactions.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
