Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/10931#issuecomment-175331775
Hmmm... I don't see how this would help much.
If you're shading one Jackson artifact, you should shade all of them.
Otherwise users can get into weird situations by mixing and matching things in
their applications. And shading all of jackson is tricky, because you have
jackson-annotations and shading annotations doesn't work well with Scala code.
Regarding the original e-mail, if someone wants to use a newer version of
jackson in their app, they have two choices:
- they need to use the `spark.{driver,executor}.userClassPathFirst` options
and include the jackson jars with their application (with `--jars` or using fat
jars)
- they need to override the version of Jackson used in Spark by provide all
Jackson artifacts in `spark.{driver,executor}.extraClassPath`.
I'd try those before trying to change anything in Spark at all.
---
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]
