You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jiayi Liao (Jira)" <ji...@apache.org> on 2020/03/22 07:05:00 UTC

[jira] [Updated] (FLINK-16597) Handle exception thrown from close method in OutputFormat

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

Jiayi Liao updated FLINK-16597:
-------------------------------
    Summary: Handle exception thrown from close method in OutputFormat  (was: Handle exception from close method in OutputFormat)

> Handle exception thrown from close method in OutputFormat
> ---------------------------------------------------------
>
>                 Key: FLINK-16597
>                 URL: https://issues.apache.org/jira/browse/FLINK-16597
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Task
>    Affects Versions: 1.10.0
>            Reporter: Jiayi Liao
>            Assignee: Jiayi Liao
>            Priority: Major
>
> If {{DataSinkTask}} fails or throws an exception, the {{OutputFormat}} will call {{tryCleanupOnError}} before {{close}}. But the calling order is reverse when {{DataSinkTask}} is cancelled, which doesn't make much sense that we can still clean the output format after it's closed.
> I'm not very sure if this is a bug. But this does mislead our developers when implementing our customized {{OutputFormat}}. cc [~sewen]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)