[jira] [Comment Edited] (HIVE-13795) TxnHandler should know if operation is using dynamic partitions

["Eugene Koifman (JIRA)" <ji...@apache.org>]

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

Eugene Koifman edited comment on HIVE-13795 at 10/16/17 10:01 PM:
------------------------------------------------------------------

HIVE-14943 adds logic lock acquisition code path to know if it's part of DP write and the delete SQL stmt is removed from addDynamicParitions()


was (Author: ekoifman):
HIVE-14943 add logic lock acquisition code path to know if it's part of DB write and the delete SQL stmt is removed from addDynamicParitions()

> TxnHandler should know if operation is using dynamic partitions
> ---------------------------------------------------------------
>
>                 Key: HIVE-13795
>                 URL: https://issues.apache.org/jira/browse/HIVE-13795
>             Project: Hive
>          Issue Type: Bug
>          Components: Transactions
>    Affects Versions: 1.3.0, 2.1.0
>            Reporter: Eugene Koifman
>            Assignee: Eugene Koifman
>            Priority: Critical
>
> TxnHandler.checkLock() see more comments around "isPartOfDynamicPartitionInsert". If TxnHandler knew whether it is being called as part of an op running with dynamic partitions, it could be more efficient. In that case we don't have to write to TXN_COMPONENTS at all during lock acquisition. Conversely, if not running with DynPart then, we can kill current txn on lock grant rather than wait until commit time.
> if addDynamicPartitions() also knew about DynPart it could eliminate the Delete from Txn_components... statement
> This is an important perf optimization when it allows us to detect that concurrent txns will have a WW conflict early



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)