[FLINK-34368][fs] Update GCS connector to 3.1.18#28511
Draft
luca-p-castelli wants to merge 1 commit into
Draft
Conversation
Assisted-By: devx/56fd221d-a91c-4f66-8ca4-ed8b0dab1e3c
Collaborator
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
Update the GCS file system connector to
gcs-connector3.1.18.This revives FLINK-34368 now that Flink no longer supports Java 8. The previous attempt (#24267) could not proceed because
gcs-connector3.x requires Java 11 or newer.Brief change log
gcs-connectorfromhadoop3-2.2.18to3.1.18flink-gs-fs-hadoop'sMETA-INF/NOTICEVerifying this change
This change is covered by the existing GCS file system build and test coverage.
Note: I had to make a fix to
gcs-connectorfor version 3.x to have a correct POM.Does this pull request potentially affect one of the following parts:
@Public(Evolving): (yes / no) noDocumentation
Was generative AI tooling used to co-author this PR?