[
https://issues.apache.org/jira/browse/HIVE-17683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16548382#comment-16548382
]
Eugene Koifman commented on HIVE-17683:
---------------------------------------
[~ikryvenko],
this looks good in general. One question:
Did you mean to add support for 'formatted' option? In patch 4, adding
'formatted' produces
{noformat}
{"LOCK INFORMATION:":"[]"}
{noformat}
{{ExplainTask.getLocks()}} has a bug
I think, {[explain locks drop table test_explain_locks}} produces
Read/WriteEntity because this table doesn't exist at the time this command runs.
> Annotate Query Plan with locking information
> --------------------------------------------
>
> 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
> Attachments: HIVE-17683.01.patch, HIVE-17683.02.patch,
> HIVE-17683.03.patch, HIVE-17683.04.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)
