[jira] [Commented] (FLINK-6306) Sink for eventually consistent file systems

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-6306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16460360#comment-16460360 ] 

ASF GitHub Bot commented on FLINK-6306:
---------------------------------------

Github user stevenzwu commented on the issue:

    https://github.com/apache/flink/pull/4607
  
    @aljoscha is there any doc/write-up about the reworking of BucketingSink?


> 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
>            Priority: Major
>         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
(v7.6.3#76005)