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

Zhu Zhu closed FLINK-30823.
---------------------------
    Resolution: Done

Done via
7894fe56cd92d423a20302ea488b075507c20bbd
886b1f155313207128ddb2a242c2d1587c6d8642
6913f91107f606db2db8e23c21ac74c4aaf63de0
401aefdcf16992bde636eb617decdfa1ffd36622
1420ee7ed69a3ce72eab8027570cc3af9fa828a3

> Enable speculative execution for some of the typical built-in sinks
> -------------------------------------------------------------------
>
>                 Key: FLINK-30823
>                 URL: https://issues.apache.org/jira/browse/FLINK-30823
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Coordination
>            Reporter: Biao Liu
>            Assignee: Biao Liu
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.17.0
>
>
> After the Sink supports speculative execution, here we enable speculative 
> execution for some built-in sinks. For each type of Sink (SinkV2, 
> SinkFunction, OutputFormat) we picked some typical sinks that do not require 
> any or only minor changes.
> In this ticket, we would enable DiscardingSink, PrintSinkFunction, PrintSink, 
> FileSink, FileSystemOutputFormat to support speculative execution.
> Speculative execution might not be meaningful for some of these sinks, like 
> DiscardingSink, PrintSinkFunction and PrintSink. However, when these sinks 
> are chained with other operators, the chained task could not support 
> speculative execution if there is any operator in chain does not support 
> speculative execution. That's the main idea behind this.
> FileSink and FileSystemOutputFormat are the most typical implementation for 
> SinkV2 and OutputFormat. We would not enable speculative execution for the 
> StreamingFileSink, because it's marked as deprecated. The HiveTableSink 
> without compaction could also support speculative, because it depends on 
> FileSystemOutputFormat.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to