-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Add AftersynchronizedProcessing Time as continuation trigger #36285
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
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
6aa47a4
Add AftersynchronizedProcessing Time as continuation trigger
tarun-google d5e42f2
fix trailing space
tarun-google d9cf159
fix trailing space
tarun-google 14a6019
fix formatting
tarun-google dd20190
Merge branch 'apache:master' into continuation_triggers
tarun-google File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
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.
Could you explain why the continuation trigger of a AfterEach trigger is a repeatedly trigger? @tarun-google
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.
@shunping With continuation trigger concept, we are injecting a new trigger after the GroupBy window. Which gets evaluated every time there is a new pane of data released by first trigger. For example if the initial trigger is AfterProcessingTime(5), which trigger only once after 5 sec. we are adding a new trigger after GroupBy when this trigger happens, which is pass by layer. A lot of our triggers are one time.
But the point with AfterEach(condition1, condition2,..) is it is not a one time trigger. it triggers every time there is a condition met. So, if we just write the continuation trigger AfterAny() then it triggers only once. we want continuation trigger for AfterEach to trigger every time the condition is met, not once.
Reference:
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.
Yea, it's not an exact science. There's no real correctness criteria for continuation trigger except "don't hold up data that is already triggered". And the only reason we don't make all of them
Repeatedly(Always)is for the corner case of aligned processing time where the user might be surprised if a downstream aggregation had many more outputs because it fired right away instead of waiting for everything aligned to the same processing time. TBH even then it is sort of meh.