-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
[BEAM-97] Input watermarks can never be null #30
Conversation
This also includes some additional comments and asserts related to pairing output watermark holds with their cleanup timers. They could be separated but since everything is around watermark hold robustness I think we should keep them together. |
Hold off on this one please. |
@kennknowles |
@kennknowles |
@@ -172,6 +172,8 @@ public boolean shouldFire(W window, Timers timers, StateAccessor<?> state) throw | |||
} | |||
|
|||
public void onFire(W window, Timers timers, StateAccessor<?> state) throws Exception { | |||
// shouldFire should be 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.
Typo? I think rootTrigger.invokeShouldFire(context)
should be true, otherwise it is forbidden to call invokeOnFire
.
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.
Done.
Nice. This makes things so much cleaner. |
PTAL |
Oh, I'm too late for the rename - will need to rebase. |
All good. |
Add ControlClientPool interface and fix broken JobResourceManagerTest
* Rewrite github_sample to 1 line * Add license to table shortcode
feat: serialize/deserialize custom coders
No description provided.