You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Robert Metzger (JIRA)" <ji...@apache.org> on 2019/02/28 11:14:00 UTC

[jira] [Updated] (FLINK-7364) Log exceptions from user code in streaming jobs

     [ https://issues.apache.org/jira/browse/FLINK-7364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Metzger updated FLINK-7364:
----------------------------------
    Component/s:     (was: Streaming)
                 Runtime / Operators

> 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 / Operators
>    Affects Versions: 1.3.1
>            Reporter: Elias Levy
>            Priority: 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
(v7.6.3#76005)