Hi Beam developers, I'm preparing a pull request (#13740) <https://github.com/apache/beam/pull/13740> that upgrades the non-vendored Guava version (currently 25.1-jre) to the latest version (30.1-jre). I want Beam to be built, tested, and run with the newer version of Guava so that its Guava dependency works with other libraries that depend on newer Guava (e.g., gcsio).
However, certain Hadoop/Cassandra-related modules in the Beam project require Guava 25 or older (Details in BEAM-11626 <https://issues.apache.org/jira/browse/BEAM-11626>) when they run tests. Therefore, this PR attempts to split guava versions: 25 for Hadoop/Cassandra-related modules and 30 for the rest of the project. I analyzed the effect of the change in the PR below. So far I see the effect is minimal thanks to the fact that Beam vendors Guava and only 3 modules declares non-test dependency to the non-vendored Guava. https://github.com/apache/beam/pull/13740 As I am not a Hadoop/Cassandra user, I might have missed important points. I appreciate it if you can share your perspective on this. -- Regards, Tomo
