[CURATOR-200] Proposal: Remove references to guava library from public APIs

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.3.0, 2.12.0
• Component/s: Framework
• Assignee: Jordan Zimmerman
• Reporter: Mike Drob
• Created: 01/Apr/15 22:24
• Updated: 10/Apr/17 19:06
• Resolved: 16/Jan/17 18:27

Description

There was a good discussion on the mailing list: http://curator.markmail.org/thread/yjete2ozm32jmz5u

The critical portion copied here:

The problem classes that I have found are:

• curator-framework: org.apache.curator.framework.listen.ListenerContainer : method forEach takes a parameter of type com.google.common.base.Function
• curator-framework: org.apache.curator.framework.api.transaction.CuratorTransactionResult : method ofTypeAndPath returns com.google.common.base.Predicate
• curator-x-discovery-server: org.apache.curator.x.discovery.server.contexts.GenericDiscoveryContext : constructor takes param of type com.google.common.reflect.TypeToken
• curator-x-discovery: org.apache.curator.x.discovery.InstanceFilter : inherits from com.google.common.base.Predicate

In the ensuing discussion, it sounded like we'd need to get started on an implementation before we had enough information to determine whether the changes are too intrusive or not.

Issue Links

• blocks: YARN-3774 ZKRMStateStore should use CuratorOp when we upgrade to Curator 3
• supercedes: CURATOR-256 Provide curator artifact in Maven Central with Guava shaded away
• supercedes: CURATOR-263 Update to Guava 18
• supercedes: CURATOR-370 Replace use of MoreExecutors.sameThreadExecutor
• links to: GitHub Pull Request #190
• links to: GitHub Pull Request #196
• links to: GitHub Pull Request #199
• links to: GitHub Pull Request #212