[ https://issues.apache.org/jira/browse/HIVE-17683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16505140#comment-16505140 ]
Eugene Koifman commented on HIVE-17683: --------------------------------------- This is very strange. The build bot ran and passed all tests.... based on https://issues.apache.org/jira/browse/HIVE-17683?focusedCommentId=16505064&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16505064. In any case, I've not had a chance to read the patch yet. > 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)