Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/1048#issuecomment-135746206
I am trying this out right now.
It stands in conflict with other pending pull requests that actually want
to get the "job-specificness" out of the Client, which means foremost dropping
the classloader in the client. This pull request bakes the classloader in even
more.
The next thing where I am unsure about is the "SerializedThrowable". I am
personally a big fan of making things explicit. If something comes back that
needs explicit deserialization, it should look like this. Currently, we hope
that everyone remembers to check whether the exception is a serialized
throwable. it not, we silently loose cause and stack trace.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
