hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Igor Kryvenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-17683) Annotate Query Plan with locking information
Date Sun, 15 Jul 2018 18:15:00 GMT

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

Igor Kryvenko commented on HIVE-17683:
--------------------------------------

[~ekoifman] Hi, Eugene.
Yeah, I can refactor it. 
Actually, I was a little bit confused too why {{drop table}} doesn't acquire any locks, but
it really produces no {{readEntity}} and {{writeEntity}}.
Also, I will add switching between JSON and default output in the following patch. 

Thanks for the review.



> 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
>
>
> 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)

Mime
View raw message