-
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
Windowing Support for the Dask Runner #32941
Conversation
- CoGroupByKey is broken due to how tags are used with GroupByKey - GroupByKey should output `[('0', None), ('1', 1)]`, however it actually outputs: [(None, ('1', 1)), (None, ('0', None))] - Once that is fixed, we may have test pipelines work on Dask.
…initial tests pass.
This reverts commit 09365f6.
…n infinite loop." This reverts commit 676d752.
…-runner-windowing
@Abacn May I have some help getting the windows build to work? It looks tractable:
|
Ok, I think I got it working on windows, too. |
1b41784
to
7caba84
Compare
I think the failing tests are just flaky. |
Hey there! I'd love to get this merged. Please let me know if there is any more I can do. |
Sorry for late response. My comments were most on the infrastructure / testing related components. For that part LGTM. For dask runner implementation would it be possible to find a reviewer who knows Dask also? |
That sounds good. Hey, @jacobtomlinson: by any chance, do you have cycles to review this PR, focusing on the Dask aspect of the code? This one has been a long time coming! I would appreciate any and all help you can offer (and no pressure if time is sparse). |
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.
Generally this looks good to me from the Dask side.
Hey @Abacn! In light of Jacob's review, do you think we're good-to-go? :) |
Thank you, merging for now |
This CL adds basic Windowing support to this runner, including a few tests for side inputs – take three (#27618, #23913).
CC: @cisaacstern
Reviewers: @jrmccluskey
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
addresses #123
), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, commentfixes #<ISSUE NUMBER>
instead.CHANGES.md
with noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.