[
https://issues.apache.org/jira/browse/FLINK-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14365219#comment-14365219
]
Robert Metzger commented on FLINK-1593:
---------------------------------------
Hey,
I'm currently testing Flink streaming and I found the
{{StreamInvokable.callUserFunctionAndLogException()}} method.
The method name indicates very much that the system is still logging exceptions
without failing the job.
Am I overseeing something or can I safely remove the method and propagate the
exception through the system?
> Improve exception handling int Streaming runtime
> ------------------------------------------------
>
> Key: FLINK-1593
> URL: https://issues.apache.org/jira/browse/FLINK-1593
> Project: Flink
> Issue Type: Improvement
> Components: Streaming
> Reporter: Gyula Fora
> Assignee: Gyula Fora
> Fix For: 0.9
>
>
> The current exception handling logic is not very helpful when trying to debug
> an application. In many cases with serialization/user code or other
> exceptions, the error is just logged and not propagated properly. This should
> mainly be fixed in the StreamInvokables.
> Some improvements that could be made:
> -Serialization/Deserialiaztion and other system errors should be propagated
> instead of just silently logged
> -User code exceptions should be better handled, for instance I think it would
> be helpful to log them to INFO so that users can instantly see it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
