Status: In Progress
Affects Version/s: None
Fix Version/s: None
Relying on Guava implementation in Hadoop has been painful due to compatibility and vulnerability issues.
Guava updates tend to break/deprecate APIs. This made It hard to maintain backward compatibility within hadoop versions and clients/downstreams.
With 3.x uses java8+, the java 8 features should preferred to Guava, reducing the footprint, and giving stability to source code.
This jira should serve as an umbrella toward an incremental effort to reduce the usage of Guava in the source code and to create subtasks to replace Guava classes with Java features.
Furthermore, it will be good to add a rule in the pre-commit build to warn against introducing a new Guava usage in certain modules.
Any one willing to take part in this code refactoring has to:
- Focus on one module at a time in order to reduce the conflicts and the size of the patch. This will significantly help the reviewers.
- Run all the unit tests related to the module being affected by the change. It is critical to verify that any change will not break the unit tests, or cause a stable test case to become flaky.
- Merge should be done to the following branches: trunk, branch-3.3, branch-3.2, branch-3.1
A list of sub tasks replacing Guava APIs with java8 features:
I also vote for the replacement of Precondition with either a wrapper, or Apache commons lang.
I believe you guys have dealt with Guava compatibilities in the past and probably have better insights. Any thoughts? Wei-Chiu Chuang, Gabor Bota, Steve Loughran, Ayush Saxena, Sean Busbey, Jonathan Turner Eagles, Kihwal Lee