You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Igor Kryvenko (JIRA)" <ji...@apache.org> on 2018/08/01 16:12:01 UTC

[jira] [Commented] (HIVE-17683) Add explain locks command

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

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

[~ekoifman] Hi, Eugene seems like failures are unrelated. I ran failed tests without my patch locally, and all of them failed too.

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