[
https://issues.apache.org/jira/browse/FLINK-7364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-7364:
----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> 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.20.1#820001)
