Github user cowtowncoder commented on the pull request:
https://github.com/apache/spark/pull/12213#issuecomment-206555763
I don't know enough about Spark internals to know if this makes sense, but
there is a smaller alternative databinding, Jackson jr:
https://github.com/FasterXML/jackson-jr
which does use Jackson's streaming parser+generator (`jackson-core`), but
not databinding. This makes it about 80% smaller to use. There is also uber-jar
variant with shaded `jackson-core`, which would remove any conflicts with
various jackson versions, with size of 350kB (jackson-jr-objects which does not
bundle jackson-core is about 75kB).
Jackson-jr does support both "untyped" access (Maps, Lists, wrappers) and
very basic Bean-binding, and there is even simple optional tree model
(jackson-jr-stree, 24kB); and performance-wise is comparable to full Jackson
databinding for most use cases.
So using this might allow removal of `jackson-databind`, and this in turn
could help with some of version compatibility problems as many spark jobs use
Jackson for their own needs.
But as I said, I don't know how heavy usage is and whether this is a
practical possibility.
---
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]
