-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Enable real-time clock in prism by default. #36473
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
R: @damccorm |
|
CC: @lostluck |
|
Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control. If you'd like to restart, comment |
damccorm
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems good to me, but my ability to review thoroughly is somewhat limited. @lostluck if you're able to take a look, that would be awesome. If not, let me know and I'll merge for now
|
I am going to get to it today. |
| timersProcessingTimePipelineBuilder(func(s beam.Scope) beam.PCollection { | ||
| now := time.Now() | ||
| return periodic.Impulse(s, now, now.Add(10*time.Second), 0, false) | ||
| return periodic.Impulse(s, now, now.Add(10*time.Second), 5*time.Second, false) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the goal here is to have the transform fire twice, not once?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Exactly!
|
Thanks a lot for your time to review! |
|
After this PR, real-time clock is enabled in prism by default. So I think we can close #32786. |
Also adjust some processing time timer tests so that they can finish before server timeout.