flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kostas Kloudas (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (FLINK-10522) Check if RecoverableWriter supportsResume and act accordingly.
Date Wed, 05 Dec 2018 14:16:00 GMT

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

Kostas Kloudas closed FLINK-10522.
    Resolution: Fixed

Merged on master with 600bd9cdbb42b709cfa6fa313648fcea317ad781
and on release-1.7 with a15a29837b9e100f21ad8e8d79821ef6b0490871

> 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
>              Labels: pull-request-available
>             Fix For: 1.8.0, 1.7.1
> 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

View raw message