Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/3658#issuecomment-71710576
Hey @pwendell, I'll try to get to this soon. But I wanted to get your
feedback on my idea for fixing the `network/` dependencies thing before I try
to implement it.
The way I see it, the cleanest way is to do the Guava shading in the
earliest artifact possible; that would be `network/common`. So that artifact
would have the honor of providing all the relocated Guava classes to everyone.
Since `spark-core` depends on it, everything should work out.
The only downside I see to that is that `network/common` would now expose
`Optional` and friends when it's not really its fault (`spark-core` demands it).
What do you think?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
