[
https://issues.apache.org/jira/browse/FLINK-6306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Seth Wiesman updated FLINK-6306:
--------------------------------
Description: 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. (was: 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 must 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. )
> 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
>
> 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.3.15#6346)
