[
https://issues.apache.org/jira/browse/FLINK-10522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16678437#comment-16678437
]
ASF GitHub Bot commented on FLINK-10522:
----------------------------------------
kl0u commented on issue #7047: [FLINK-10522] Check if RecoverableWriter
supportsResume() and act accordingly.
URL: https://github.com/apache/flink/pull/7047#issuecomment-436675707
R @azagrebin
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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.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)
