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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
