cnauroth opened a new pull request, #26160: URL: https://github.com/apache/flink/pull/26160
## What is the purpose of the change Upgrade GCS connector to 2.2.26. ## Brief change log Upgrade the [GCS Connector](https://github.com/GoogleCloudDataproc/hadoop-connectors/tree/v2.2.26/gcs) bundled in the Flink distro from version 2.2.18 to 2.2.26. [Release Notes](https://github.com/GoogleCloudDataproc/hadoop-connectors/blob/v2.2.26/gcs/CHANGES.md) ## Verifying this change This change is already covered by existing tests. I also have the new integration tests from #26102 patched in locally. (I would prefer for that test PR to be merged first, so that we have more testing confidence on these upgrades in the future.) ``` mvn -Pfast -pl flink-filesystems/flink-gs-fs-hadoop clean verify ``` For testing the documentation changes, I attempted to build locally, but I encountered an unrelated error that I haven't investigated yet. ``` cd docs ./build_docs.sh -p ... ERROR render of "section" failed: "/usr/local/google/home/cnauroth/git/apache/flink/docs/layouts/_default/baseof.html:24:5": execute of template failed: template: _default/list.html:24:5: executing "_default/list.html" at <partial "docs/html-head" .>: error calling partial: execute of template failed: html/template:partials/docs/html-head.html:33:13: no such template "_internal/google_analytics_async.html" ``` ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): yes - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: no - The serializers: no - The runtime per-record code paths (performance sensitive): no - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no - The S3 file system connector: no (but yes to the GCS connector) ## Documentation - Does this pull request introduce a new feature? no - If yes, how is the feature documented? not applicable -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
