Skip to content
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

[Flink][WIP] Support using with Flink 1.18 #2871

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

auroranockert
Copy link

Which Delta project/connector is this regarding?

  • Spark
  • Standalone
  • Flink
  • Kernel
  • Other (fill in here)

Description

This adds changes to support using Delta with Flink 1.18.

Work in progress

  • Decide if the Flink version we build against really should be changed to 1.18.1
  • Update the README with version numbers that actually support newer Flink
  • Fix the Mima settings so that it does not think that things in io.delta.flink.internal are actually exposed API.

I think these should be done as separate PRs but I am not sure, depending on what you think I'll either do another PR for the Mima things or fix it properly in here.

How was this patch tested?

It was tested via the test suite (on Java 8, running on arm64 macOS) and some minor manual testing.

[info] Passed: Total 568, Failed 0, Errors 0, Passed 565, Skipped 3
[success] Total time: 1142 s (19:02), completed Apr 9, 2024 4:36:35 PM

If you have any ideas on how to better test this I would love to know, since I think I can see a patch to support Flink 1.19 in my future and would love to be more confident in that one.

Does this PR introduce any user-facing changes?

No. It should not beyond supporting a newer version of Flink.

Thanks

Thanks to @sdahlbac and @oskarskog for helping me with this, I definitely would not have had the patience to run the test suite this many without them.

This adds the relatively minor changes required to support Flink 1.18

 - Calcite has a new version of Janino that breaks API
 - The newer Flink Hive catalog has some new more specific type requirements internally

Signed-off-by: Aurora Nockert <aurora@nockert.se>
This commit most likely should not exist, the breakage is just in the internal namespace but I have no idea how to signal to Mima that this is not an actual API breakage.

Signed-off-by: Aurora Nockert <aurora@nockert.se>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant