Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/10441#issuecomment-166765248
> Note that my exception changes were actually motivated by a case where
this error-handling logic swallowed other internal exceptions and only printed
"1" as output. The problem is that the try-catch blocks here are capable of
intercepting exceptions which occur as a result of internal programming errors
/ violated assumptions, not just bad user input.
Okey. Let's print the whole stack trace. LGTM
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
