Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/12775#issuecomment-217661490
Sorry, I haven't been completely clear while thinking through this issue.
There are two basic considerations: 1) Is NoClassDefFoundError benign enough in
this context that we can actually catch that particular Error here and handle
it essentially the same as we currently do for ClassNotFoundException? 2) In
the case of other Errors, instead of telling the scheduler about just this
particular task failure, should we be doing something different or additional
in a higher-level, more general case Error catcher?
---
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]
