Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/22234
From my understanding, yea. The problem here is sounds like ambiguity in
empty strings since they can be interpreted as empty strings and also `null`.
To me, this is actually rather a bug since we can't distinguish, and don't
respect the empty value. If empty strings are written, they should be read as
empty strings.
This PR proposes an ability explicitly set the empty value to work around
the behaviour change.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
