GitHub user mshields822 opened a pull request:
https://github.com/apache/incubator-beam/pull/118
[BEAM-162] Sensible interaction of merging and closed triggers
Same bug, better approach.
- We always check for closed triggers on the post-merged window state.
- We are careful not to leak NEW windows.
- More unit tests.
- Along the way, discovered we were clearing trigger finished bits.
Since TriggerRunner does not currently have its own unit tests,
added new unit test in ReduceFnRunnerTest to hit that specific case.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mshields822/incubator-beam beam-162
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-beam/pull/118.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #118
----
commit 55c34a553264491bd42db4197793eff436858b73
Author: Mark Shields <[email protected]>
Date: 2016-04-04T20:31:12Z
Clear finished bits from merged-away windows, not merge result window.
commit 69eb778b354cd63fb23a48789c93ed48c2a01961
Author: Mark Shields <[email protected]>
Date: 2016-03-31T18:36:01Z
Check for closed windows post-merging rather than pre-merging.
Make sure we garbage collect NEW windows which end up being for closed
windows.
Add unit tests to confirm.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
