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

Posted to issues@flink.apache.org by "Kostas Kloudas (JIRA)" <ji...@apache.org> on 2018/10/10 13:39:00 UTC

[jira] [Updated] (FLINK-10522) Check if RecoverableWriter supportsResume and act accordingly.

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

Kostas Kloudas updated FLINK-10522:
-----------------------------------
    Summary: Check if RecoverableWriter supportsResume and act accordingly.  (was: Check if RecoverableWriter supportsResume and accordingly.)

> Check if RecoverableWriter supportsResume and act accordingly.
> --------------------------------------------------------------
>
>                 Key: FLINK-10522
>                 URL: https://issues.apache.org/jira/browse/FLINK-10522
>             Project: Flink
>          Issue Type: Sub-task
>          Components: filesystem-connector
>    Affects Versions: 1.6.0
>            Reporter: Kostas Kloudas
>            Assignee: Kostas Kloudas
>            Priority: Major
>             Fix For: 1.7.0
>
>
> So far we assumed that all `RecoverableWriters` support "resuming", i.e. after recovering from a failure or from a savepoint they could keep writing to the previously "in-progress" file. This assumption holds for all current writers, but in order to be able to accommodate also filesystems that may not support this operation, we should check upon initialization if the writer supports resuming and if yes, we go as before, if not, we recover for commit and commit the previously in-progress file.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)