-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Support DataStream batch for portable flink runner and run validation runner tests #37133
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
Conversation
Summary of ChangesHello @Abacn, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request represents the initial phase of introducing Apache Flink 2 support into the project. It primarily focuses on foundational build system adjustments and a critical functional update. The build changes are designed to handle Flink 2's new requirements, such as a higher Java version and changes in its core APIs, by implementing flexible source overrides and conditional dependencies. Additionally, it ensures that the Flink portable runner respects the Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
fbb46f2 to
35d1b32
Compare
35d1b32 to
73c7684
Compare
73c7684 to
25a2844
Compare
|
1 failing test: |
c914121 to
63e5f2c
Compare
|
Assigning reviewers: R: @liferoad for label build. Note: If you would like to opt out of this review, comment Available commands:
The PR bot will only process comments in the main thread (not review comments). |
|
Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control. If you'd like to restart, comment |
* Honor getUseDataStreamForBatch pipeline option for Flink portable runner * Refactor gradle scripts in preparation for Flink 2 support * Create a PostCommit run validate runner tests on legacy DataSet
63e5f2c to
f57e4db
Compare
damccorm
left a comment
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 lgtm - just had a couple minor comments/questions, but they don't need to block merging for now
| } | ||
|
|
||
| def pushContainers = project.rootProject.hasProperty(["isRelease"]) || project.rootProject.hasProperty("push-containers") | ||
| def containerName = project.parent.name.startsWith("2") ? "flink_job_server" : "flink${project.parent.name}_job_server" |
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.
Why do we no longer need a separate container with flink 2?
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.
Oh I see - you're moving to a tag approach. Maybe we could just do this generally for all versions? It would be nice to not need a new container each 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.
Sorry, this is part of #31631 (updated PR description now). Also noted there I intended to make this change in new Flink (major) version to avoid breaking existing users.
|
|
||
| def overrides(versions, type, base_path) { | ||
| versions.collect { "${base_path}/${it}/src/${type}/java" } + ["./src/${type}/java"] | ||
| // order is important |
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.
Why does order matter?
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.
For file A.java in flink/1.18/src, it is consumed by flink/1.18, flink1.19, flink1.20,...
If in Flink 1.19 it needs to be overriden again, this order makes sure that flink1.20 is consuming A.java in flink/1.19 dir
|
This is great effort! 👍 |
The main purpose of this PR is to start exercising validation runner tests for Flink portable runner with useDataStreamForBatch enabled. As DataSet API is removed in Flink 2, all batch workflows will use DataStream API.
Honor getUseDataStreamForBatch pipeline option for Flink portable runner
Refactor gradle scripts in preparation for Flink 2 support, including
Please add a meaningful description for your change here
Part of #36947
Fix #31631
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.mdwith 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.