singhravidutt opened a new pull request, #23933:
URL: https://github.com/apache/flink/pull/23933
## What is the purpose of the change
Shade the guava version required specifically by google-cloud-storage.
## Brief change log
Introduced dependency on guava version(`31.1-jre`) required by
`google-cloud-storage`. Upgrade of `google-cloud-storage` lead to runtime
failure because of new functionalities added in `31.1-jre`.
This change pins guava version to the one required by storage client
specifically in `flink-gs-fs-hadoop`, leaving all other filesystem
implementation untouched.
## Verifying this change
This change is already covered by existing tests. These tests pass with the
new version.
```
mvn -Pfast -pl flink-filesystems/flink-gs-fs-hadoop clean test
```
Created a cluster by replacing binaries specific to `flink-gs-fs-hadoop` and
ran the following job
```
gcloud dataproc jobs submit flink --cluster <cluster-name> --region
us-central1 --jar file:///usr/lib/flink/examples/streaming/WordCount.jar --
--input gs://vinaylondhe-public/word_count/word_count.txt --output
gs://vinaylondhe-public/rdsingh_wc_output
```
Earlier it was failing with following error
```
Caused by: java.lang.NoSuchMethodError:
'com.google.common.collect.ImmutableMap
com.google.common.collect.ImmutableMap$Builder.buildOrThrow()'
```
Execution for the same job successful now with these changes.
## 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
## 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]
