pan3793 commented on code in PR #7883:
URL: https://github.com/apache/hadoop/pull/7883#discussion_r2284125866
##########
hadoop-tools/hadoop-gcp/pom.xml:
##########
@@ -427,6 +427,11 @@
<dependencyManagement>
<dependencies>
+ <dependency>
+ <groupId>com.google.guava</groupId>
+ <artifactId>guava</artifactId>
+ <version>33.1.0-jre</version>
Review Comment:
the https://github.com/google/guava/blob/v33.4.8/README.md says:
> 2. APIs without `@Beta` will remain binary-compatible for the indefinite
> future. (Previously, we sometimes removed such APIs after a deprecation
> period. The last release to remove non-`@Beta` APIs was Guava 21.0.)
Even
> `@Deprecated` APIs will remain (again, unless they are `@Beta`). We
have no
> plans to start removing things again, but officially, we're leaving our
> options open in case of surprises (like, say, a serious security
problem).
So Guava seems to ensure backward compatibility since 22, except for `@Beta`
API? Suppose the GCS client does not use `@Beta` API, it is seems to be safe
and simple to always use the latest Guava in the whole Hadoop project?
--
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: common-issues-unsubscr...@hadoop.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
