Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/2984#issuecomment-61781966
Hey @vanzin I was actually thinking that over time we might shade a handful
of things in addition to guava. The user classpath first is at best a partial
solution (and I agree, we should try to make that actually work correctly)
because it only deals with cases where either Spark or the application don't
actually use conflicting parts of a library. In many cases, there is a
legitimate conflict, especially with libraries like jetty that are widely used.
In these cases it seems like shading the dependency is the only real answer,
because Spark and user code need to exist in the same JVM - and even in the
same threads - at the same time.
---
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]
