hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eugene Koifman (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-13795) TxnHandler should know if operation is using dynamic partitions
Date Thu, 26 May 2016 17:57:12 GMT

     [ https://issues.apache.org/jira/browse/HIVE-13795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Eugene Koifman updated HIVE-13795:
----------------------------------
    Description: 
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


  was:
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


> 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
>            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.3.4#6332)

Mime
View raw message