Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18645
The JSON error arises because now, JSON messages contain an explicit entry
for null properties, like `"message" : null`. This looks like a small behavior
change introduced in Jackson 2.7. See
https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.7 Although it's the
same, semantically, in theory, we should make the behavior identical.
It looks like several places in the code explicitly configure Jackson to
only include `NON_NULL` properties. I believe it needs to be extended to be set
explicitly elsewhere now. Still investigating ...
---
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
