[
https://issues.apache.org/jira/browse/HIVE-17683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Koifman updated HIVE-17683:
----------------------------------
Resolution: Fixed
Fix Version/s: 3.2.0
Status: Resolved (was: Patch Available)
> Add explain locks <sql> command
> -------------------------------
>
> Key: HIVE-17683
> URL: https://issues.apache.org/jira/browse/HIVE-17683
> Project: Hive
> Issue Type: New Feature
> Components: Transactions
> Reporter: Eugene Koifman
> Assignee: Igor Kryvenko
> Priority: Critical
> Fix For: 3.2.0
>
> Attachments: HIVE-17683-branch-3.patch, HIVE-17683.01.patch,
> HIVE-17683.02.patch, HIVE-17683.03.patch, HIVE-17683.04.patch,
> HIVE-17683.05.patch, HIVE-17683.06.patch
>
>
> Explore if it's possible to add info about what locks will be asked for to
> the query plan.
> Lock acquisition (for Acid Lock Manager) is done in
> DbTxnManager.acquireLocks() which is called once the query starts running.
> Would need to refactor that.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
