-
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-12277] Add flink 1.13 build target. #14719
Conversation
Run Java PreCommit |
Can you please change beam/.test-infra/jenkins/CommonTestProperties.groovy Lines 28 to 30 in cc29b5b
Also can you add 1.13 to the website https://github.com/apache/beam/blob/cc29b5b308b6ed91d787449b8105cc0b292273ac/website/www/site/content/en/documentation/runners/flink.md |
Also add a note on CHANGES.md -> 2.31.0 -> New Features |
and
|
Besides the things Ismaël pointed out, we also need INFRA to create a new docker repo: INFRA-21833 |
Docker repo seems to be up now https://hub.docker.com/r/apache/beam_flink1.13_job_server |
retest this please |
Run Flink ValidatesRunner |
Run Java Flink PortableValidatesRunner Batch |
Run Java Flink PortableValidatesRunner Streaming |
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.
LGTM
Arrghh seems metrics are broken for the Portable runner. Can you maybe what is the deal @ibzib ? |
Looks like it's hitting an NPE while unregistering metrics because the taskExecutorManager is null. This seems like a Flink bug to me -- if registers these metrics, they should remain accessible even after the slot manager has been shut down. Getting these metrics should probably return 0 rather than NPE.
|
Or perhaps these metrics should be unregistered when the slot manager is shut down, before the taskExecutorManager is nulled out. |
I don't think this is a regression, I'm pretty sure we've seen this in prior versions too. Maybe we can pull this into separate issue? |
I think this boils down to whether we want to wait for the issue being fixed in Flink or we want a "quick-win" solution 🤔 Maybe we can temporarily work around this in FileReporter, before fixing the issue upstream? |
Run Flink ValidatesRunner |
Run Java Flink PortableValidatesRunner Batch |
Run Java Flink PortableValidatesRunner Streaming |
issue with PR on the flink's side - https://issues.apache.org/jira/browse/FLINK-22646 |
Run Flink ValidatesRunner |
Run Java Flink PortableValidatesRunner Batch |
Run Java Flink PortableValidatesRunner Streaming |
Looks like the metric name formatting changed, I added a commit to update it. |
Run Flink ValidatesRunner |
Run Java Flink PortableValidatesRunner Batch |
Run Java Flink PortableValidatesRunner Streaming |
Run Java PreCommit |
i think there is not an RC1 yet so maybe we can convince the release manager to get it in, but well in that case we got to solve the still open jacoco issue to get this into master first. |
What is the next step on this PR? I would not recommend cherry picking this to the current release. |
As far as I know there's one outstanding issue, the Java precommit failure with Jacoco. We won't cherry pick this. Maybe 2.31.0. |
Looks like it was just a typo in the source overrides. I added another commit to fix it. @dmvk can you rebase this? |
Run Java PreCommit |
I rebased it (and push forced it) since the conflict was on my commit. This should be good now! |
Run Java PreCommit |
Run Flink ValidatesRunner |
Run Java Flink PortableValidatesRunner Batch |
Run Java Flink PortableValidatesRunner Streaming |
Run Java Spark PortableValidatesRunner Batch |
https://issues.apache.org/jira/browse/BEAM-12277
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
R: @username
).[BEAM-XXX] Fixes bug in ApproximateQuantiles
, where you replaceBEAM-XXX
with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.CHANGES.md
with noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
ValidatesRunner
compliance status (on master branch)Examples testing status on various runners
Post-Commit SDK/Transform Integration Tests Status (on master branch)
Pre-Commit Tests Status (on master branch)
See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI.