Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/1048#issuecomment-134226512
I had some comments. The main question is why do we introduce a new
`JobFailure` message instead of treating a `SerializedThrowable` as what it is,
namely a `Failure`. If we let `SerializedThrowable` extend `Exception`, then we
could send the serialized throwable over the network using a `Failure`, like
any other exception. Thus there are no duplicate code paths. Only at the
receiving end, we have to check for a `SerializedThrowable` and deserialize the
wrapped exception to obtain the original value.
---
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.
---
