Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/17902
> do you think its important to include jackson at this level?
I wouldn't say "important", but rather that it's a nice default. Jackson
seems to be everywhere from core onwards, and even the other use I had for this
(shuffle service, which I didn't change because it has some clever usage of
keys that does not map to the code here well) uses Jackson.
I can easily remove Jackson and let anyone implement their own; but really
the only implementation we'll have in Spark is Jackson-based (and some other,
probably Java serialization, for the tests here), so it didn't feel like a big
gain.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
