Github user steveloughran commented on a diff in the pull request:
https://github.com/apache/spark/pull/12004#discussion_r113749971
--- Diff: pom.xml ---
@@ -621,6 +621,11 @@
<version>${fasterxml.jackson.version}</version>
</dependency>
<dependency>
+ <groupId>com.fasterxml.jackson.dataformat</groupId>
+ <artifactId>jackson-dataformat-cbor</artifactId>
--- End diff --
yes, keeping jackson in sync is a key breakage point. Declaring it in the
root POM doesn't add it everywhere, it just delares it so that the cloud POM
can exclude the one which comes via the `aws-java-sdk-s3` dependency JARs and
pick up the one used in spark. The (later) Spark one is compatible with the one
aws SDK depends on, so moving up works...it's just that all jackson bits needs
to be in sync, and there's no way in Maven or Ivy to declare that fact.
---
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]
