Details
-
Bug
-
Status: Resolved
-
Blocker
-
Resolution: Invalid
-
3.0.0-alpha4
-
None
-
None
Description
HADOOP-10101 upgraded the guava version for 3.x to 21.
Guava is broadly used by Java projects that consume our artifacts. Unfortunately, these projects also consume our private artifacts like hadoop-hdfs. They also are unlikely on the new shaded client introduced by HADOOP-11804, currently only available in 3.0.0-alpha2.
We should shade Guava everywhere to proactively avoid breaking downstreams. This isn't a requirement for all dependency upgrades, but it's necessary for known-bad dependencies like Guava.
Attachments
Attachments
Issue Links
- is broken by
-
HADOOP-10101 Update guava dependency to the latest version
- Resolved
- is related to
-
HADOOP-14386 Rewind trunk from Guava 21.0 back to Guava 11.0.2
- Resolved
-
HADOOP-16924 Shade & Update guava version to 29.0-jre
- Resolved
- relates to
-
HADOOP-11804 Shaded Hadoop client artifacts and minicluster
- Resolved
-
YARN-7028 Backport HADOOP-14386 to YARN-5355 branch
- Resolved
-
HADOOP-15960 Update guava to 27.0-jre in hadoop-project
- Resolved
-
HADOOP-13363 Upgrade protobuf from 2.5.0 to something newer
- Open
-
HADOOP-14238 [Umbrella] Rechecking Guava's object is not exposed to user-facing API
- Resolved
- links to