[
https://issues.apache.org/jira/browse/HIVE-11914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14945949#comment-14945949
]
Eugene Koifman commented on HIVE-11914:
---------------------------------------
Partly because the modified code path is part of Streaming API path, but mostly
because it there were no other tests that covert heartbeat logic in Streaming
API.
> When transactions gets a heartbeat, it doesn't update the lock heartbeat.
> -------------------------------------------------------------------------
>
> Key: HIVE-11914
> URL: https://issues.apache.org/jira/browse/HIVE-11914
> Project: Hive
> Issue Type: Bug
> Components: HCatalog, Transactions
> Affects Versions: 1.0.1
> Reporter: Eugene Koifman
> Assignee: Eugene Koifman
> Attachments: HIVE-11914.2.patch, HIVE-11914.patch
>
>
> TxnHandler.heartbeatTxn() updates the timestamp on the txn but not on the
> associated locks. This makes SHOW LOCKS confusing/misleading.
> This is especially visible in Streaming API use cases which use
> TxnHandler.heartbeatTxnRange(HeartbeatTxnRangeRequest rqst)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
