Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16651
Let's close this if there is no follow-up
---
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
en
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16651
Ping @sharkdtu
---
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
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16651
I'm not clear why you believe the exception handling should be changed. If
IOExceptions are fatal, and this is a form of I/O exception (corrupted input),
why change it?
---
If your project is set u
Github user sharkdtu commented on the issue:
https://github.com/apache/spark/pull/16651
@srowen
i think the logs were just for `MalformedInputException`, it does't matter
that non-IOExceptions will be rethrown, because they will be catched by upper
callers.
---
If your project
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16651
Isn't this changing the default behavior for non-IOExceptions? now they're
rethrown.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16651
Can one of the admins verify this patch?
---
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 feat
