[FLINK-39647] Downgrade presto-hive to 0.294#28180
Merged
Merged
Conversation
Collaborator
spuru9
approved these changes
May 17, 2026
Contributor
spuru9
left a comment
There was a problem hiding this comment.
LGTM.
Dont we check flink build across java versions?
Contributor
Author
we do only for nightlies for regular PR only jdk17 check |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is the purpose of the change
The reason is that current 0.297 requires jdk17
as a result all CIs with jdk11 are failing (example: https://github.com/apache/flink/actions/runs/25897801260/job/76114449425)
0.294 was the last still able to run with jdk11
Brief change log
pom, NOTICE
Verifying this change
ci, also link to my work with nightly where jdk11 is green
https://github.com/snuyanzin/flink/actions/runs/25988702580
Does this pull request potentially affect one of the following parts:
@Public(Evolving): ( no)Documentation
Was generative AI tooling used to co-author this PR?