Consider the create table function (parts removed for simplicity):
A potential openTransaction() / commitTransaction() mismatch can occur if the is_table_exits() method call experiences a connection failure.
Since get_table() in is_table_exists() uses executeWithRetry(), the transaction will be rolled back and get_table() will be called again if the is a connection problem. However, this rollback and retry will reset the global openTransactionCalls counter back to 0, effectively canceling out the openTransaction() call.
Then later in the method when commitTransaction() is called, Hive will throw an error similar to the following:
Caused by: java.lang.RuntimeException: commitTransaction was called but openTransactionCalls = 0. This probably indicates that there are unbalanced calls to openTransaction/commitTransaction
A similar problem exists with create_type_core()