… has been a constant pain w.r.t compatibility etc.
Should we consider adopting a policy to not use guava in Common/HDFS/YARN?
MR doesn't matter too much since it's application-side issue, it does hurt
end-users though since they still might want a newer guava-version, but at
least they can
Guava did make the lives of Hadoop development easier in many cases -- What
I've been consistently hearing is that the version of Guava used is Hadoop
is so old that it starts to hurt the application developers.
I appreciate the value of Guava -- things like CacheMap are fairly
difficult to
Haohui Mai created HADOOP-11287:
---
Summary: Simplify UGI#reloginFromKeytab for Java 7+
Key: HADOOP-11287
URL: https://issues.apache.org/jira/browse/HADOOP-11287
Project: Hadoop Common
Issue
As Haohui Mai said, removing the dependency on the Guava may not be a good
idea.
But, instead can we use a fixed guava version in Hadoop which is stable as
of now, with a shaded package structure ?
so that it will not break the application level dependency on another
version of the Guava. Inside
