Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18865
Based on the original PR https://github.com/apache/spark/pull/2680 and the
current behavior, we do not think the current behavior is by design. The usage
cases you mentioned above are rare. When selecting `_corrupt_record`, most
users are expecting to get the all the rows that we fail to parse. Now, the
returned results do not cover all the scenarios.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
