[
https://issues.apache.org/jira/browse/FLINK-20337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238592#comment-17238592
]
Kostas Kloudas commented on FLINK-20337:
----------------------------------------
[~maguowei] I think that all this could become a single issue because all these
changes depend on each other. If someone in the future wants to see what were
the steps for backwards compatibility of the {{FileSink}}, then all these
changes would be relevant and not a subset of them. What do you think?
> 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
> Fix For: 1.12.0
>
>
> 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 provide a way for the user who uses `StreamingFileSink` to migrate
> from `StreamingFileSink` to `FileSink`.
> For this purpose we propose to let the new sink writer operator could load
> the previous StreamingFileSink's state and then the `SinkWriter` could have
> the opertunity to handle the old state.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
