Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/12433#issuecomment-210725264
Hmm, this is unfortunate. It looks like there are a bunch more assertions
like the one in the `FutureAction` test suite which match on the class / name
of the exception thrown from methods which call `Await.result`. I wonder
whether this change of wrapping the exception is going to cause regressions in
user code which tries to do the same thing.
Should I try to use reflection to make a best-effort attempt to re-throw
using the same exception?
---
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]
