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
[FLINK-12092] [docs]Clarify when onTimer(...)
is called
#8106
Conversation
Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community Automated ChecksLast check on commit 81f7ac0 (Wed Dec 04 14:51:28 UTC 2019) Warnings:
Mention the bot in a comment to re-run the automated checks. Review Progress
Please see the Pull Request Review Guide for a full explanation of the review process. The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commandsThe @flinkbot bot supports the following commands:
|
event-/processing-time instants. When a timer's particular time is reached, the `onTimer(...)` method is | ||
called. During that call, all states are again scoped to the key with which the timer was created, allowing | ||
event-/processing-time instants. The `onTimer(...)` method is | ||
called when such an event-time is first caught up by a watermark or such a processing-time is reached. During that call, all states are again scoped to the key with which the timer was created, allowing |
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.
I agree we should explain what "when time is reached" means for both event and processing time, but I'm not sure of the actual changes in the PR.
Maybe something along the lines of:
When a timer's particular time is reached, the `onTimer(...)` method is called; for processing time, this would mean __________, while for event time, this would mean ______________.
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.
@alpinegizmo what do you think?
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.
I suggest:
With event-time timers, the onTimer(...)
method is called when the current watermark is advanced up to or beyond the timestamp of the timer, while with processing-time timers, onTimer(...)
is called when wall clock time reaches the specified time.
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.
I don't have a strong opinion about wording as long as it explains things clearly.
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.
@an0 can you update the PR to what David suggested?
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.
Sure. Done.
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.
@tzulitai Is it mergeable?
@flinkbot attention @alpinegizmo |
onTimer(...)
is calledonTimer(...)
is called
onTimer(...)
is calledonTimer(...)
is called
Hi @an0 thank you for your contribution and sorry for a late reply. I will merge it now. |
No description provided.