[
https://issues.apache.org/jira/browse/HIVE-24468?focusedWorklogId=519849&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-519849
]
ASF GitHub Bot logged work on HIVE-24468:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 03/Dec/20 20:01
Start Date: 03/Dec/20 20:01
Worklog Time Spent: 10m
Work Description: belugabehr edited a comment on pull request #1728:
URL: https://github.com/apache/hive/pull/1728#issuecomment-738274162
@pvary
I agree with your understanding that the SELECT FOR UPDATE is a lock, and
therefore the timestamps should be always increasing, but imagine if the HMS
clock on two instances were off by 5s (or more). The HMS with the slower clock
would generate events that were earlier in time, but with a higher ID. So
there is not strong enforcement of the time being sequential. It's all based
on the HMS clocks being in sync and trusting those clocks.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 519849)
Time Spent: 1h 20m (was: 1h 10m)
> Use Event Time instead of Current Time in Notification Log DB Entry
> -------------------------------------------------------------------
>
> Key: HIVE-24468
> URL: https://issues.apache.org/jira/browse/HIVE-24468
> Project: Hive
> Issue Type: Improvement
> Reporter: David Mollitor
> Assignee: David Mollitor
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
