[
https://issues.apache.org/jira/browse/FLINK-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14699782#comment-14699782
]
Aljoscha Krettek commented on FLINK-1028:
-----------------------------------------
I don't think it is relevant anymore. I tried adding an exception in a
constructor and it was properly propagated. I'm closing the issue.
> Certain exceptions are not visibly reported to the user
> -------------------------------------------------------
>
> Key: FLINK-1028
> URL: https://issues.apache.org/jira/browse/FLINK-1028
> Project: Flink
> Issue Type: Bug
> Components: Distributed Runtime, TaskManager
> Reporter: Aljoscha Krettek
>
> When I throw a RuntimeException in a user code method I get the Exception in
> my IDE or on the terminal (when using the CLI client). When I throw an
> exception in the constructor of a TypeComparator the exception is only logged
> but not presented to the user. The code continues and at some later point
> fails with something that seems unrelated, making it very hard to find the
> original cause.
> Does anyone know why it is like that? Is it like this on purpose?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
