[
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 stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or 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: Minor
> Labels: auto-deprioritized-major, stale-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)
