Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/12775#issuecomment-217660452
@kayousterhout I agree with that much. My concern is whether we can expect
to successfully do even that much in the case of the more extreme Errors, or
whether we should be letting those percolate up. In the case of
NoClassDefFoundError, logging a little more information and continuing as we do
with ClassNotFoundException seems like the right thing to do.
---
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]
