Github user srowen commented on the issue:
https://github.com/apache/spark/pull/21596
Yes, long term that is the right thing to do. It still introduces a
user-visible classpath change, which is why I'm on the fence about doing so in
Spark 2.4. I feel like several people out there use Jackson in their app and
probably end up inheriting the Spark version and then it disappears for them.
Not impossible, but needs to be weighed against the upside: is it some
medium-sized bug fixes and performance gain? tough call.
I'd be all for resolving this in Spark 3.0 though.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
