[
https://issues.apache.org/jira/browse/FLINK-20337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guowei Ma updated FLINK-20337:
------------------------------
Description:
Flink-1.12 introduces the `FileSink` in FLINK-19510, which can guarantee the
exactly once semantics both in the streaming and batch execution mode.
We need to figure out how to migrate from `StreamingFileSink` to `FileSink` for
the user who uses the `StreamingFileSink` currently.
For this purpose we propose to let the new sink writer operator could load the
previous sink's state and then the `SinkWriter` could have the chance to handle
the old state.
was:
Flink-1.12 introduces the `FileSink` in FLINK-19510, which can guarantee the
exactly once semantics both in the streaming and batch execution mode.
We need to figure out how to migrate from `StreamingFileSink` to `FileSink` for
the user who uses the `StreamingFileSink` currently.
The pr wants provide a way that make it possible.
> Make migrate `StreamingFileSink` to `FileSink` possible
> -------------------------------------------------------
>
> Key: FLINK-20337
> URL: https://issues.apache.org/jira/browse/FLINK-20337
> Project: Flink
> Issue Type: Improvement
> Components: API / DataStream
> Affects Versions: 1.12.0
> Reporter: Guowei Ma
> Priority: Blocker
>
> Flink-1.12 introduces the `FileSink` in FLINK-19510, which can guarantee the
> exactly once semantics both in the streaming and batch execution mode.
> We need to figure out how to migrate from `StreamingFileSink` to `FileSink`
> for the user who uses the `StreamingFileSink` currently.
> For this purpose we propose to let the new sink writer operator could load
> the previous sink's state and then the `SinkWriter` could have the chance to
> handle the old state.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
