flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aljoscha Krettek (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FLINK-6306) Sink for eventually consistent file systems
Date Thu, 03 May 2018 11:18:00 GMT

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

Aljoscha Krettek updated FLINK-6306:
    Priority: Critical  (was: Major)

> 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
>            Priority: Critical
>             Fix For: 1.6.0
>         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

View raw message