You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/08/27 21:37:01 UTC
[jira] [Commented] (FLINK-6306) Sink for eventually consistent file
systems
[ https://issues.apache.org/jira/browse/FLINK-6306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143229#comment-16143229 ]
ASF GitHub Bot commented on FLINK-6306:
---------------------------------------
Github user sjwiesman closed the pull request at:
https://github.com/apache/flink/pull/3752
> Sink for eventually consistent file systems
> -------------------------------------------
>
> Key: FLINK-6306
> URL: https://issues.apache.org/jira/browse/FLINK-6306
> Project: Flink
> Issue Type: New Feature
> Components: filesystem-connector
> Reporter: Seth Wiesman
> Assignee: Seth Wiesman
> Attachments: eventually-consistent-sink
>
>
> Currently Flink provides the BucketingSink as an exactly once method for writing out to a file system. It provides these guarantees by moving files through several stages and deleting or truncating files that get into a bad state. While this is a powerful abstraction, it causes issues with eventually consistent file systems such as Amazon's S3 where most operations (ie rename, delete, truncate) are not guaranteed to become consistent within a reasonable amount of time. Flink should provide a sink that provides exactly once writes to a file system where only PUT operations are considered consistent.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)