galenwarren commented on pull request #15599: URL: https://github.com/apache/flink/pull/15599#issuecomment-1013896727
@xintongsong @rmetzger @zentol The CI build [succeeded](https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=29496&view=results)! Running locally with dependency-convergence enabled didn't yield anything to resolve, there weren't multiple versions of any particular artifact. However, `google-cloud-storage` pulled in a version of `grpc-context` that was different from the version of different grpc-related artifacts (`grpc-api`, `grpc-auth`, etc.) through `gcs-connector`. Using @zentol's suggestion to force the grpc versions to be consistent using the `grpc-bom` entry in `dependencyManagement` did the trick. (And I think that @rmetzger's solution was essentially the same, in effect.) I still don't know that I understand why this is required in the CI environment, but honestly I'm not bothered by it if you all aren't. Going forward, we will have to keep the `fs.gs.grpc.version` property set to the highest version of grpc-related artifacts pulled in via `google-cloud-storage` and `gcs-connector` but that should be all. I added a comment in the pom file. So is everyone good with this solution? If so, then I'll proceed to squash all the commits. Thanks everyone for your help. -- 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]
