You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Aron Hamvas (Jira)" <ji...@apache.org> on 2020/01/16 08:30:00 UTC
[jira] [Commented] (HIVE-22341) abortTxns statements should be
executed in a single transaction
[ https://issues.apache.org/jira/browse/HIVE-22341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17016683#comment-17016683 ]
Aron Hamvas commented on HIVE-22341:
------------------------------------
Hi [~jcamachorodriguez],
Both me and [~dkuzmenko] checked this, and we are confident that abortTxns is handled in one single MySQL transaction on the HMS side. Unless there is a misunderstanding regarding your requirement on our side, I think this can be closed. :)
> abortTxns statements should be executed in a single transaction
> ---------------------------------------------------------------
>
> Key: HIVE-22341
> URL: https://issues.apache.org/jira/browse/HIVE-22341
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Reporter: Jesus Camacho Rodriguez
> Priority: Major
>
> Logic in `abortTxns` should be executed in a single transaction, rather than multiple ones. Otherwise, if you restart HMS between txn abort and the lock deletion, we end up with orphaned locks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)