[
https://issues.apache.org/jira/browse/FLINK-7364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17328735#comment-17328735
]
Flink Jira Bot commented on FLINK-7364:
---------------------------------------
This major issue is unassigned and itself and all of its Sub-Tasks have not
been updated for 30 days. So, it has been labeled "stale-major". If this ticket
is indeed "major", please either assign yourself or give an update. Afterwards,
please remove the label. In 7 days the issue will be deprioritized.
> Log exceptions from user code in streaming jobs
> -----------------------------------------------
>
> Key: FLINK-7364
> URL: https://issues.apache.org/jira/browse/FLINK-7364
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Task
> Affects Versions: 1.3.1
> Reporter: Elias Levy
> Priority: Major
> Labels: stale-major
>
> Currently, if an exception arises in user supplied code within an operator in
> a streaming job, Flink terminates the job, but it fails to record the reason
> for the termination. The logs do not record that there was an exception at
> all, much less recording the type of exception and where it occurred. This
> makes it difficult to debug jobs without implementing exception recording
> code on all user supplied operators.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
